On 2006-10-20, Max Dyckhoff <[EMAIL PROTECTED]> wrote:
> Hi all,
>
> :verbose map << shows nothing. I have no mappings with << at the
> start (or in fact, anywhere in the mapping).
>
> Removing the two ,, mappings did nothing useful. The only
> "interesting" map that I have is one right at the end of the list
> which is some non-printing character duplicating another mapping I
> have for <C-S-+>. I have no idea how to identify this character.
>
> I agree that plugins shouldn't set the localleader, but in
> fairness I don't ever use the local leader for anything other than
> the vimoutliner plugin so I'm not too worried.
>
> Any more ideas as to what I could try?
You could try determining which plugin is causing the problem.
1. Choose a file that you've been editing when you've seen the
problem and start vim as you normally would, e.g., "vim
somefile", and verify that you see the problem.
2. Using the same file, start vim as "vim -N -u NONE somefile"
and verify that you don't see the problem.
3. Start vim as "vim --noplugin somefile" and see if you see
the problem. (You may have to comment-out any "filetype"
lines in your .vimrc as well.) If you do see the problem,
the cause is in your .vimrc; otherwise, the problem is in a
plugin.
The best strategy for tracking down the problematic plugin depends
on how many private plugins you have and of which kinds. I would
start by turning off all filetype detection in your .vimrc so that
only ordinary plugins are loaded, then try "vim somefile" and see
what happens. If you still see the problem, then I would rename
half the files in your ~/.vim/plugin directory with a dummy
extension (.hide?) and repeat the experiment, doing a binary search
on the file sets until you narrow it down to the problematic plugin.
You can use the :scriptnames command during this process to see
which plugins are actually being sourced.
HTH,
Gary
--
Gary Johnson | Agilent Technologies
[EMAIL PROTECTED] | Wireless Division
| Spokane, Washington, USA
