Saturday, July 9, 2011

Re: Plugin/addon managers

Excerpts from Eric Weir's message of Sat Jul 09 19:17:54 +0200 2011:
> Again, I have brief experience with Pathogen. I've bookmarked the Vim
> pages for vim-addon-manager and Vundle. I'd appreciate any feedback or
> guidance on these or other plugin managers I may have overlooked. Any
> insights will be welcome, of course, but I'd be especially interested
> in comments of people who have experience with more than one of these
> or other plugins.

VAM was designed to go out of your way. This means if a plugin doesn't
work its a bug. You should either create a ticket or contact me so that
we can find a fix (by mail or irc).
This may result in plugin patches though - cause not all plugins like
being installed into a directory separate from ~/.vim.

VAM's documentation contains a section comparing it to Pathogen.
The reason why I recommend VAM over Pathogen is its "dependency
resolving" feature even if its a quick and dirty - it'll help the Vim
community to reuse code which in turn will result in more reviews ...

The second major feature is its community managed "plugin pool" which
allows you to install plugins by name.

The plugin pool also allows us to tag plugins as being superseded by
other ones. Eg if upstream has changed you'll get an additional
confirmation question before the plugin is installed telling you about
which plugin we'd prefer.

IMHO you should be using a management system. My choice is VAM - but I'm
definitely biased :)

Marc Weber

--
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

No comments: