Reply to message «Re: which plugin management system to use?», sent 23:35:51 23 March 2011, Wednesday by Israel Chauca F.:
> I see. Point 2 suggest to me that VAM will source plugins that have an
> after dir even when Vim starts up, is that so? That's what I understood
> when I was considering it to manage my rtp and that was the reason for me
> to choose something else. As I wrote before, I don't mind restarting Vim
> after installing a plugin.
It would not be doing it if vim did sourcing of `after' directory. Just a hack
for plugins that use directory that are not supposed to be used by anyone but
the user itself (and user is supposed to use this directory only for plugins
that are enough poorly designed to unconditionally override
mappings/options/...
defined by user). And VAM is not `sourcing plugins that have after directory'.
It sources vim files in `after' directory on VimEnter event, not the whole
plugin.
Original message:
> On Mar 23, 2011, at 2:20 PM, ZyX wrote:
> > 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).
>
> I don't use VAM to manage my rtp, it's just to show the idea.
>
> >> 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.
>
> Ditto.
>
> >> 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.
>
> That might be important or not, if it is, don't use multiple dirs. But if
> it's not, use as many dirs as you need.
>
> >> 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'))
>
> I wasn't implying that VAM should support this, just pointing out that the
> rtp manager could handle it by itself through the interface.
>
> >> 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.
>
> I see. Point 2 suggest to me that VAM will source plugins that have an
> after dir even when Vim starts up, is that so? That's what I understood
> when I was considering it to manage my rtp and that was the reason for me
> to choose something else. As I wrote before, I don't mind restarting Vim
> after installing a plugin.
>
> Israel
signature.asc
Description: This is a digitally signed message part.
