Excerpts from Eric Weir's message of Sat Jan 07 19:13:15 +0100 2012:
> I believe the command needed is ActivateAddons {}.
So how does this "ActivateAddons {}" tell VAM which plugin you want?
How did you read the docs causing this conclusion?
{name} is to substituted by the real name. You can also try tab
completion.:
:ActivateAddons org<c-d>
And you'll get a list including vim-orgmode without {}.
Thus do this only:
ActivateAddons vim-orgmode
Still ActivateAddons is inefficient. THat's why I strongly recommend you
to start reading docs from the beginning - there are headlines.
You want to follow this one:
2 Installation & installing plugins |VAM-installation|
Hard to imagine how you've been able to miss it.
> In that connection I don't understand how the
> vim-addon-manager-known-repositories plugin is to be used.
the VAM code takes care about it. Everything does work automatically -
when using the SetupVAM sample function, see docs.
The known-repositories repositories is separating the plugin information
from core code installing the plugins. That's all about it.
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
