On Mar 21, 8:16 pm, "Israel Chauca F." <israelvar...@fastmail.fm> wrote: > * I don't like having a list of plugins in my vimrc.
I manage plugins in a separate file like this: let s:bundlerc = $MYVIMDIR . '/vimbundlerc' " or: let s:bundlerc = globpath(&rtp, 'vimbundlerc') if filereadable(s:bundlerc) exec 'source ' . s:bundlerc endif > * I have multiple bundle dirs and some times I have two versions of the same > plugin, I like to be able to choose which one should be disabled. I like to have the plugins stored in the directory named as I choose, so I have something like the following in vimbundlerc: " PLUGIN: x/indentPython: https://github.com/vim-scripts/indentpython.vim.git " call s:Add(['x/indentPython']) " PLUGIN: x/indentPython2: https://github.com/vim-scripts/indentpython.git call s:Add(['x/indentPython2']) The separate (Python) downloader script then downloads the scripts into correct directories under .bundles. I prefer to enable the plugins in a two step process. First I Add() the plugins I want, then I Activate() the added plugins. I find it easier to disable the plugins I don't want by commenting out the Add() lines. The main purpose of Activate() is to set up the runtimepath. I like to configure the plugins only if they are activated so I have blocks like this in vimbundlerc: if s:Has('indentPython2') " ... endif if s:Has('bufexplorer') map <S-F3> \\be endif I created my own system because at the time I didn't know of a system that would support all the desired features. Marko -- 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
