присланное в 14:59:19 25 сентября 2010, Суббота,
отправитель Tom Link:
> 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.
Yes, third clause is ambigious. Removed it, thanks.
Текст сообщения:
> > 1 Sorry, but my vimpluginloader is a library for developers.
> > 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
No comments:
Post a Comment