3 ms·
A few people have mentioned vimballs as a plugin solution. There are (at least) two other potential solutions for plugin handling: Pathogen and Vimana. Pathogen
by telemachos 16y ago
A few people have mentioned vimballs as a plugin solution. There are (at least) two other potential solutions for plugin handling: Pathogen and Vimana. Pathogen is what the blog author is actually using already, but he didn't realize it initially. He refers to a .vim repo on Github that "does some magic where [it] puts each plugin in its own directory under /~.vim/bundles/." What he describes here is based on Tim Pope's Pathogen: basically a plugin to manage all other plugins. I've been using Pathogen for a bit now, and it's excellent. Another solution is Cornelius Lin's Vimana, which I've heard very good things about, but I haven't tried. Some links below.
http://github.com/tpope/vim-pathogen http://github.com/tpope/vim-pathogen
http://tammersaleh.com/posts/the-modern-vim-config-with-pathogen http://tammersaleh.com/posts/the-modern-vim-config-with-path...
http://ithaca.arpinum.org/2010/06/28/vim-updates.html http://ithaca.arpinum.org/2010/06/28/vim-updates.html
http://github.com/c9s/Vimana http://github.com/c9s/Vimana
- xtho 16y agoThere are other similar solution for handling "bundles" (or plugins distributed as git repositories): tpugin (on demand path manipulation): http://github.com/tomtom/vimtlib/blob/master/macros/tplugin.vim http://github.com/tomtom/vimtlib/blob/master/macros/tplugin.... scriptmanager: http://github.com/MarcWeber/vim-addon-manager http://github.com/MarcWeber/vim-addon-manager