John Little wrote: > On Jun 23, 7:14 am, Torsten Andre <[email protected]> wrote: > >> Can you guys tell me how you organize your key mappings? ..[. > > Even if the plugins' mappings don't conflict, I dislike having pages > of mappings lying around; I sometimes use ad hoc mappings, and want to > type :map to see where I'm at. Plugins can be carefully set up to use > the autoload stuff, but the mappings are part of the interface so are > normally defined always. > > So I've been driven to hacking the interface script of plugins, so > that there's one map or command that sets up its interface. F. ex., > I'm a fan of Dr Chip's Align.vim, and he has factored the maps into > AlignMapsPlugin.vim, so I just move that out of the plugin directory > and have a couple of frequently used maps in my .vimrc, and one that > invokes AlignMapsPlugin.vim to get the whole deal. > > Regards, John >
Thanks you two for your ideas. If I understood everything correctly there is optimal way to handle this stuff. Choices are to edit the plugins or to overwrite the mappings made therein in the after directories. Is there a way to restore all mappings to default while removing newly defined ones? For example the latex suite plugin defines some mappings I don't even need/use. I'd prefer them to be unmapped, but to unmap them all manually seems to be overkill. I think what would be a good compromise is to restore default mappings (or delete all user defined mappings) and then load my own mappings within the after directories. Is this possible? Cheers, Torsten -- 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
