> 2 It does not fetch anything neither itself nor with vim-addon-manager,
> 3 but is able to source
> runtime dependencies when they are required (that is why it is pluginloader).
Based on the description on vim.org and clause 3, I had the impression
that it solves the same problem as tplugin (which could be described
with 3 too). tplugin-loader doesn't rely on extra work on part of the
developer (1) though, which is why it probably isn't? But maybe I just
don't get it.
Regards,
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
No comments:
Post a Comment