> 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).
Thanks for the detailed response, Marc.
I need to check out the documentation. Does VAM itself do the actual installation? Or do you have to set up the folders to comply with the requirements of VAM and the plugins being installed? Do you identify and select plugins from within VAM? Or do you somehow "inform" VAM that you have a plugin you want to install?
> This may result in plugin patches though - cause not all plugins like
> being installed into a directory separate from ~/.vim.
As I recall, that was the problem in trying to get VimOutliner to run after being installed under Pathogen.
> 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 ...
I think I understand what it means to "resolve dependencies. I don't understand the comment on the effect of the feature.
> 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.
Pretty attractive features, the receding one included.
> IMHO you should be using a management system. My choice is VAM - but I'm
> definitely biased :)
The documentation addresses installation under Windows and Linux. I'm on a Mac and using MacVim. Can I use it?
It also lists dependencies of the addon. How do I determine if I've got them. My OS X is 10.6.8.
You recommend cloning from git for users of git. I know git as a repository of plugins, addons, scripts, etc. I get the sense it's much more than that. Also that "using" it involves much more than downloading plugins, etc. and associated files. And that it's probably not something I need to get involved with, i.e., that I would be getting in way over my head [I am not a programmer], that it's not something I need, other than as a repository of plugins, etc.
Installation instructions give some code to be added to your vimrc. I thought I wasn't ever supposed to do anything to vimrc, only vimrc.
Thanks again -- and again in advance,
------------------------------------------------------------------------------------------
Eric Weir
Decatur, GA USA
eeweir@bellsouth.net
--
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:
Post a Comment