On 2012-07-31, ping wrote:
> I tried these debugging tools but still have no clear clue.
> I even tried vim -V temp1.log or vim -V4 temp1.log, the 1st part of
> the result flushed away from my screen and I couldn't capture
> anything into here, from the rest of the output I couldn't find
> anything related to /etc/vim
If you immediately follow the -V argument by a filename (i.e.,
without an intervening space), the debug information will be
captured to that file instead of being spewed across your screen. I
think level 2 will capture what we're interested in here.
vim -V2verboselog [other arguments]
Regards,
Gary
--
You received this message from the "vim_use" maillist.
Do not top-post! Type your reply below the text you are replying to.
For more information, visit http://www.vim.org/maillist.php
No comments:
Post a Comment