On 01/14/2011 06:16 AM, Pablo Giménez wrote:
> :verbose nmap p
> n p *@:wincmd p<CR>:<BS>
> Last set from /user_data/.tmp/v837878/56
>
> Has somebody has the same problem, or can give me more ideas to debug
> the problem?
Pablo,
Here are a couple of things to try (since it looks like you are
on a Unix-like platform):
- Make sure the problem doesn't appear when running Vim without
any plugins or your .vimrc::
vim -u NONE
- Grep for the mapping string in your ~/.vim directory, and
possibly in $VIMRUNTIME. To display $VIMRUNTIME from within
Vim::
:echo $VIMRUNTIME
It's likely to be below /usr/share/vim.
One of these searches might turn up something interesting::
egrep -iR 'p<cr>:<bs>' ~/.vim /usr/share/vim
egrep -iR 'wincmd.*\<p\>' ~/.vim /usr/share/vim
egrep -iR 'wincmd' ~/.vim /usr/share/vim
You may need to adjust the search patterns, since the culprit
might be building up the mapping from pieces. But most
likely, the full word "wincmd" will appear somewhere near the
vimscript that's to blame, so the last pattern would probably
work (though it may have many false hits).
- Make a backup of your ~/.vim directory and your ~/.vimrc, then
start removing plugins and re-testing until the problem goes
away.
Michael Henry
--
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
