On Mar 24, 2014 3:50 AM, "Israel Chauca" <israelvarios@fastmail.fm> wrote:
>
> On 3/23/14, 11:34 AM, Bram Moolenaar wrote:
>>
>>
>> At some point Vim started supporting plugins. At that time it was fine
>> to add a plugin manually, it was a one-time thing. But now that there
>> are so many plugins and they get updated often, manually updating
>> plugins has become tedious.
>>
>> I am wondering what Vim users like about plugin managers.
>
>
> I use Pathogen for the following reasons:
> - Allows to have every plugin segregated in its own directory.
> - It's posible to have more than one "bundle" dir. At least in my clone.
> - Leaves the plugin management up to the user. It doesn't install/remove/update plugins.
> - Individual plugins can be temporarily disabled by filtering them out of the runtimepath at start up.
> - The configuration is dead simple.
>
>
>> Is there one that works best, that everybody should use?
>
>
> Since we don't have a canonical source for plugins, I doubt that any plugin manager will be able to handle the current and future multitude of sources and formats on which plugins are and will be available.
VAM is handling this matter rather good. There is no problem in handling 99% of plugins since they are either hosted on github or on www.vim.org in though wide, but limited variety of archive formats.
You can also extend VAM to use any function to install plugin thus adding support for any VCS that is not yet supported.
>> Are there still features that no existing plugin manager offers?
>
>
> I can think of only one "feature" that could make a plugin manager a viable tool: to be a built-in feature of Vim (I'd prefer a solution in VimL, but one in C would make me happy too) and use vim.org as the only source for plugins.
www.vim.org lacks very huge number of features. Look at pypi.python.org: it is an example of a good package index. At least www.vim.org must have an API. It would also be handy to specify location of development version, things like maturity status and license.
And you are mistaking if you think there is no built-in plugin manager: there is GLVS that uses www.vim.org as source. Have you heard of anybody using it? VCS support nowadays is an ultimate requirement, www.vim.org may be the only source of information about plugins (which is a very bad idea because it does not even have HTTPS), but using VCS during installation step should be required.
>
>
>> Vundle appears to be popular, someone mentioned it's better than
>> Pathogen. So nobody is using Pathogen?
>
>
> Without being a plugin manager Pathogen is still a popular choice and, given its simplicity, I doubt that that will change any time soon.
>
>
>> But then there is also NeoBundle. But not everybody has git installed
>> and it depends on that.
>>
>> And there also is vim-addon-manager. And Vimball.
>>
>> Is it fine to have a choice of plugin managers, or is this causing a
>> headache (for users and/or for plugin writers). If yes, then we should
>> pick one plugin manager and retire the others.
>
>
> I think it's good to have choices, but I also think that having a built-in plugin manager that uses a single source would be even better. It would allow to concentrate the work on a single project, a simplest project since it wouldn't have to handle multiple sources and formats. It could even provide a base for external plugins to provide additional features, as is to be expected of every aspect of vim.
Bad idea. You cannot live in real word thinking that there may be the only format which will be adopted by everybody, especially by plugin authors that are effectively dead (no activity on www.vim.org, may be as well dead IRL).
>
> Cheers!
> Israel
>
>
> --
> --
> 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
>
> --- You received this message because you are subscribed to the Google Groups "vim_use" group.
> To unsubscribe from this group and stop receiving emails from it, send an email to vim_use+unsubscribe@googlegroups.com.
> For more options, visit https://groups.google.com/d/optout.
--
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
---
You received this message because you are subscribed to the Google Groups "vim_use" group.
To unsubscribe from this group and stop receiving emails from it, send an email to vim_use+unsubscribe@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
No comments:
Post a Comment