On 2010-05-15, meino wrote: > Ben Fritz [10-05-15 18:44]: > > > > > > On May 15, 12:51 am, [email protected] wrote: > > > AK <[email protected]> [10-05-15 07:24]:
> > > > On 05/14/2010 11:51 PM, [email protected] wrote: > > > > Try :verbose map { > > > > > > Ok, it shows me, that {<CR> is mapped to some code of a plugin. > > > That was somehow exspected, wasn't it? ;) > > > : unmap {<CR> > > > says "no such mapping"... > > > > > > > First, this is probably an insert-mode mapping. You'll need to > > use :verbose map! and :iunmap instead of :verbose map and :unmap > > above. > > > > Secondly, if you really had done :verbose map! instead of just :map, > > you should have seen exactly what file is responsible for creating the > > map. > Thanks for the hint. > Yes, I saw, what file/plugin is doing the mapping. I wrote before, > that I dont want to edit that file. If you look at that plugin, you may find that it has a global variable that you can set in your ~/.vimrc to inhibit that mapping or set of mappings. Lacking that, once you find the unmap command that works to remove that mapping, you can put that unmap command in a ~/.vim/after/ftplugin/<filetype>.vim file. That is assuming that the plugin that sets the mapping is a filetype plugin. HTH, 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
