sent 03:01:53 10 July 2011, Sunday
by Eric Weir:
> I need to check out the documentation. Does VAM itself do the actual
> installation?
Yes.
> Or do you have to set up the folders to comply with the
> requirements of VAM and the plugins being installed?
No.
> Do you identify and
> select plugins from within VAM? Or do you somehow "inform" VAM that you
> have a plugin you want to install?
You have to tell VAM the name of the plugin you want to use and put this into
vimrc: unlike pathogen with its runtime_append_all_bundles (or such, don't
remember exactly) VAM has
call vam#ActivateAddons(['addon-name', ...])
. It won't do anything without request. Guessing the name of the plugin is more
complex, I usually grep list of known repositories.
> > 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.
You mean «help the Vim community to reuse code which in turn will result in more
reviews»? I use this because it lets developers use features provided by one
plugin without forcing users to install them manually. Thus I and other
developers can have libraries like frawor, tlib, lh-vim-lib, textobj-user and
others.
> The documentation addresses installation under Windows and Linux. I'm on a
> Mac and using MacVim. Can I use it?
There is a number of archive tools you should have which are standart on linux
and curl. I don't know whether they are present on mac by default.
> It also lists dependencies of the addon. How do I determine if I've got
> them. My OS X is 10.6.8.
They are installed automatically.
> 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.
If you are not going to modify plugins all you need to know about git is that it
should be on your system. I personally suggest not to do that: you may find out
that dev version (which will be installed if you have required SCM (which is git
for most plugins)) is broken compared to release. Though you will also find out
that SCM version has some bug fixes that are not in latest release yet.
> 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.
What does «supposed to do anything to vimrc, only vimrc» mean?
Original message:
> On Jul 9, 2011, at 4:46 PM, Marc Weber wrote:
> > 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
No comments:
Post a Comment