On Mar 21, 2011, at 5:18 AM, Marc Weber wrote: > I'd personally say VAM - but others seem to think differently about it. > So I started a file which should help you find your tool of choice: > https://github.com/MarcWeber/vim-addon-manager/blob/vam-vs/VAM-VS.txt > (This list is based on the link list found on vim-scripts.org/vim/tools.html) > > I'm interested in: > > - did the authors know about VAM when starting their projects? > If so why did they still start a new project? > If not how to make it more likely that users stumble upon VAM?
I use modified pathogen [1] that uses a file to handle disabling plugins and it relies on VAM to install/remove/(update pending since VAM was going to change that functionality) plugins, with support for completion. > - What features do users like / dislike. * Easy installation/removing/update of plugins. * Simple handling of runtimepath. * I don't like having a list of plugins in my vimrc. * 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. * Doing all the plugin operations from the command line. > - make it easier for users to find out whether they should use VAM or > a different solution. > > I personally don't see a point in maintaining a plugin managers if > others already do so. So if the outcome of this comparison is that other > prefer other management systems (for whatever reason) I'll consider > stopping support for VAM and joining those projects. > I don't want to duplicate work .. What I find most useful of VAM is the plugin management functionality. That's why I forked pathogen and integrated the plugin management functionality from VAM plus the features I mentioned up there. I can't say if you should or not keep working on VAM, but I'd like to have something like that to handle my plugins. Israel [1] https://github.com/Raimondi/vim-pathogen -- 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
