Activating a plugin does not cause much overhead , only a path to
&runtimepath is added unless the plugin also has plugin/*.vim files.
So make me understand what's wrong with always activating the plugin?
Why is it that costly that you want to avoid it?
Of course adding 'dependencies-to-be-installed-only' is no issue.
However I'd like to avoid complexity if possible.
We may end up creating a github issue before taking any actions so that
all people involed (eg ZyX) can think 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
Subscribe to:
Post Comments (Atom)
No comments:
Post a Comment