On Oct 14, 2:11 am, Martin Lundberg <[email protected]> wrote: > Well, I would say it depends on what the plugin is doing. In my case > I'm doing a buffer switcher and I would like to be in control of the > mappings. I know there are many such plugins already but I'm using > this to learn vim scripting. > > I found mapclear yesterday but it doesn't seem to work. Should I add > <buffer> so that it only does it for the plugin buffer? I tested but > it's still waiting for the second ctrl-n.
What are you trying to accomplish by removing all mappings? Usually, you do not care about mappings set by other plug-ins, if some interfere with your plug-in you can always override them, as Ben mentioned. > > On Thu, Oct 14, 2010 at 6:46 AM, Ben Fritz <[email protected]> wrote: > > > On Oct 13, 3:45 pm, Martin Lundberg <[email protected]> wrote: > >> Hi, > > >> I don't want to do that becuase then it will only unmap my specific > >> mapping and if someone else uses the plugin they will probably have > >> other mappings. > > >> -Martin > > > It's rude enough when plugins override existing maps without warning. > > It would be MUCH WORSE to remove mappings that don't even collide with > > the default plugin mappings. I say, leave it alone and unmap your own > > specific command. > > > -- > > 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, visithttp://www.vim.org/maillist.php -- 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
