Reply to message «Re: which plugin management system to use?», sent 21:56:42 23 March 2011, Wednesday by Israel Chauca F.:
> Listing every plugin like this:
>
> call Activate(plugin1, plugin2, plugin3,...)
If you have more then 20 plugins, you will have to use
``vam#ActivateAddons([plugin1, plugin2, ...])'' (note the brackets).
> call Activate(plugin1)
> call Activate(plugin2)
You may try using command `ActivateAddons' after first call to
`vam#ActivateAddons'. Though it does not fix the fact that all plugins that you
use are to be explicitely activated.
> bothers me, I prefer to just list the dirs:
>
> call Use(dir1, dir2)
This will break the fact that to reproduce the configuration on other system
all
you need is to clone ~/.vimrc (+~/.vim with short ftplugins), then VAM will
install required plugins on startup. Without multiple directories I have a dump
at ~/.vam ... but I do not care much about it as I know plugin names that I
want
to make use of without activating and zsh has very good completion.
> True, but there is no reason why the rtp manager couldn't handle that task.
You want a command such as `RenameAddon {a} {b}'? It is easy to write it by
yourself (untested):
command -nargs=+ RenameAddon call call("rename", map([<q-args>],
'g:vim_addon_manager.plugin_root_dir . "/" . v:val'))
> Does activation implies VAM sourcing the files? If so, I don't like it, I
> really want to just modify rtp and let Vim do its job. I don't care that
> much if I have to restart Vim after installing/removing plugins.
It implies it only under one of two conditions:
1. Vim has already started, so it won't source anything when you modify rtp.
2. Plugin has `after' directory.
Original message:
> On Mar 21, 2011, at 7:01 PM, Marc Weber wrote:
> > 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?
>
> Listing every plugin like this:
>
> call Activate(plugin1, plugin2, plugin3,...)
>
> or
>
> call Activate(plugin1)
> call Activate(plugin2)
> ...
>
> bothers me, I prefer to just list the dirs:
>
> call Use(dir1, dir2)
>
> > 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 prefer this approach, as I explain below.
>
> >> * 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..
>
> True, but there is no reason why the rtp manager couldn't handle that task.
>
> >> * 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"?
>
> Well, that was a part of it.
>
> I chose pathogen as my rtp manager basically for one reason, its
> simplicity. One line in my vimrc would allow all the magic to unfold and
> modify my rtp.
>
> But there were some shortcomings at the moment, it was a bit too simple to
> our taste. So we (bairui on #vim and I) worked on extending pathogen with
> the following ideas:
>
> - Support multiple 'bundle' dirs.
> - Persistent enabling/disabling of plugins across vim sessions. We use a
> file to store that information, so it's like the solution you offered up
> there. - A command line interface
>
> For the plugin management, we wanted a 100% VimL solution with support for
> most of the formats on which plugins are available. So, seeing that VAM
> seemed to support being used as a library and it supported a lot of the
> crazy formats Vim scripts are available, we extended our recently added
> command line interface to use VAM as the plugin manager.
>
> > 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?
>
> See my previous answer.
>
> > How do you select the one or the other set of plugins when you need
> > them?
>
> We haven't implemented this yet, all 'bundle' dirs are used. but I was
> thinking that giving a partial or absolute path would be enough to select
> one of them. Since we have a list command that shows all bundle dirs and
> plugins, we could put numbers to every line of the output and work like
> :ls and :buffer.
>
> > 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.
>
> I'm not sure about your example, would you have a command for every set of
> plugins? When it's implemented the way to do this should be
>
> :Plugin bundle disable bundleA
>
> or something similar.
>
> Does activation implies VAM sourcing the files? If so, I don't like it, I
> really want to just modify rtp and let Vim do its job. I don't care that
> much if I have to restart Vim after installing/removing plugins.
>
> Israel
signature.asc
Description: This is a digitally signed message part.
