Marc Weber wrote:
Excerpts from Pablo Giménez's message of Thu Apr 26 20:00:23 +0200 2012:
I dont know exactly how it works but this is what it is doing ans is great.
AFAIK in vam you have to activate the plugins manually using
ActivateAddons, then the plugin rather than being waiting to be called it
is loaded.
There is a 'func not defined' hook which can be used. Maybe that is
used.
You're right, VAM does not support such yet.
Feel free to use VAM to :InstallAddons only and use tplugin for
activating them.
My understanding of pludins is:
plugin/*.vim: everything the user can customize (settings, interface,
mappings, commansds)
plugin/*.vim holds scripts that will be loaded. Customization is a
totally different issue, and is often done by setting variables in .vimrc.
autoload/*: everything else
autoload/*.vim holds scripts that will be loaded on demand; ie. when a
mapping or command in a plugin/something.vim script attempts to call a
function of the form
something#AFunction(), then autoload/something.vim will be loaded and
then the function call performed. This process does require that the
plugins be written/changed to accomodate this style.
That's why I wrote AsNeeded -- it introduces a new folder (AsNeeded/, of
course), wherein scripts reside that are not particularly written for
the autoload method. It makes a pass through scripts in that directory
and builds a single file, ANcmds.vim, that contain just enough to
support commands, sourcing the AsNeeded/function.vim scripts on demand.
It doesn't support building maps that way, though. There's a command
":AN somefile.vim" that will source an AsNeeded script, too.
Regards,
Chip Campbell
--
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
