Excerpts from Andrew Stewart's message of Fri Feb 14 13:11:56 +0000 2014: > Personally I found all the plugin managers too heavy In which way? .. VAM separates activation from installation. The "pathogen" like part is only about 700 loc (which still is much, I agree).
Collaboration doesn't mean all code must be contained in a plugin (leading to code bloat). Having a nice search (everybody could use) would be fun, too. At the moment we have: vam.mawercer.de vim-scripts.org (having trouble with duplicate script names) search at vim.sf.net ... > P.S. If you're curious: https://github.com/airblade/voom :-) I'll add it to the wiki. Improvements I see: --depth 1 cloning is faster (but failed on google accounts in the past). And this thread was about 'trying out many solutions fast' :) I like the "simple list of plugins" - and VAM / vim-pi recently implemented a proposal which could be used to share the plugin list: https://bitbucket.org/vimcommunity/vim-pi/issue/95 Because VAM turns names into dictionaries now, you could just do 'github:repo/name' 'github:repo2/name2' { 'name': 'php-plugin', .. if you need more add options such as lazy load if ft is php } { 'name': 'php-plugin', 'flavour':'latex-development' } The main reason behind this switch is that I feel supporting parallel installs can be done in Vim (like NeoBundle does) - but I feel a python script or such would do a better job, because Vim was never written to do such. Also you could try different install/management methods and use what works best for you. Marc Weber -- -- You received this message from the "vim_dev" 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 --- You received this message because you are subscribed to the Google Groups "vim_dev" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/groups/opt_out.
