Hi,
> I love how fast vim loads using tplugin and how it changes the runtime path
> on demand.
> But then I also found some limitations. Seems thare is no way to tell the
> tool not to load some plugins, also the dependency system looks a little but
> clunky because it is based on files rather than bundles.
I'm not sure what you mean by "not loading plugins". Since version 0.14, you
can define "shallow" root directories. Plugins in such a directory can be
loaded by means of the :TPlugin command but shouldn't be automatically loaded
if you call one if its commands or functions etc.
Dependency handling can admittedly be improved. tplugin knows three ways of
handling dependencies:
(1) Don't handle dependencies and load plugins as needed (this won't work if a
plugin tests if another plugin was already loaded by checking the existence of
a variable)
(2) Check if a plugins checks for the existence of loaded_PLUGIN_NAME (this
requires that the plugin authors adhered to the formatting rules which they
probably didn't :-)
(3) Use the info in *-addon-info.txt files if the plugin provides one.
If the above fails, you can define a file _tplugin_PLUGIN_NAME.vim to define
dependencies like:
call TPluginDependencies('THIS_PLUGIN', ['OTHER_PLUGIN'])
I guess you could put this definitions also into vimrc.
HTH
Tom
--
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
