On 2012-07-31, ping wrote:
> On 07/31/2012 11:08 AM, Gary Johnson wrote:
> >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]
> thanks! that's another good tip to learn about debugging vim.
>
> so I tried that:
> vim -V2temp-vim-verbose-log temp1.log
>
> and from the result temp-vim-verbose-log file I couldn't find a match
> on /etc/vim:
> ping@640g-laptop:~$ grep "/etc/vim" temp-vim-verbose-log
> ping@640g-laptop:~$
[...]
> and only 1 file contains an close entry:
> "/usr/share/vim/vimrc"
> 51 " Source a global configuration file if available
> 52 if filereadable("/etc/vim/vimrc.local")
> 53 source /etc/vim/vimrc.local
> 54 endif
> 55
It's odd that someone would put system/local Vim configuration files
in both /usr/share/vim and /etc. In my experience, package
maintainers choose one or the other.
Somewhere in that temp-vim-verbose-log file there should have been a
message about /etc/vim/ftdetect/asciidoc_filetype.vim, so maybe I
had the level wrong. ":help 'verbose'" lists the levels and what
they do. Maybe 8 would work better. (I usually just set 15 and go
searching through the mess that results.)
What are you running on that laptop? If a Linux distribution, which
one?
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