Hi Israel Chauca F,
> On Mar 21, 2011, at 5:18 AM, Marc Weber wrote:
> * I don't like having a list of plugins in my vimrc.
Can you elaborate?
Also keep in mind that you can use htis:
call vam#Activate(map(glob("~/vim-addons/*"),' fnamemodify( something
)'))
Then only the list of installed plugins will be activated.
Also you could place the list into a file and load that using readfile?
Would this feel better to your taste?
> * 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.
If the plugins you have two versions of are VCS driven plugins or if you
don't want to update them you can rename the paths easily and then
activate the new name rather than the one which has been used when
installing..
> * Doing all the plugin operations from the command line.
See other thread. Separating installation from activation would allow
that.
> 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.
So was this all caused by "I don't want to put a plugin list into
~/.vimrc"?
Does the solution shown above which automatically finds installed
plugins to activate (thus add to rtp) satisfy your needs?
Or does pathogen provide more features you care about?
How do you select the one or the other set of plugins when you need
them?
Eg the VAM way would be:
command ActivateAdditionalPluginsA ActivateAddons additional-A
command ActivateAdditionalPluginsB ActivateAddons additional-B
There are rare cases where order of activation matters.
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
