4 ms·

See also pathogen [1] and vundle [2]. [1] https://github.com/tpope/vim-pathogen https://github.com/tpope/vim-pathogen [2] https://github.com/gmarik/Vundle.vim

See also pathogen [1] and vundle [2]. [1] https://github.com/tpope/vim-pathogen https://github.com/tpope/vim-pathogen [2] https://github.com/gmarik/Vundle.vim https://github.com/gmarik/Vundle.vim

fndrplayer13 12y ago
Yeah - why should a user switch over from Pathogen or Vundle? I'm not trying to be a jerk -- just suggesting that that explanation is probably worth giving.
- phlyingpenguin 12y ago
  The biggest reason over Pathogen is automatic installation of your dependent plugins. Biggest reasons over Vundle is parallel downloading, dynamic plugin loading, and static plugins. (all of the reasons for me, YMMV) I've found even that I can install vim-plug with only a few lines of vimscript so that I don't even need to store a .vim directory in my dotfiles repository. Everything can just be installed and run the first time I start vim on a machine, and I can easly :PlugUpdate to get updates to any of my installed plugins.
  - saidajigumi 12y ago
    FWIW, this is also quite possible with Vundle. I keep my plugin management in a separate file which also contains the Vundle bootstrap logic for new systems. This stanza sets up Vundle if it isn't already installed...: https://github.com/jwhitley/vimrc/blob/master/.vim/bootstrap/bundles.vim#L7 https://github.com/jwhitley/vimrc/blob/master/.vim/bootstrap... ... and this one after the plugin definitions installs the remaining bundles: https://github.com/jwhitley/vimrc/blob/master/.vim/bootstrap/bundles.vim#L96 https://github.com/jwhitley/vimrc/blob/master/.vim/bootstrap... (I haven't updated this to the new "Plugin" Vundle syntax yet; the change is local but not pushed.) That said, features like vim-plug's postupdate hooks are sweet.
- junegunn 12y ago
  The most obvious benefit I believe is its ability to update plugins in parallel. A GIF [1] shows that it managed to update 40 plugins in mere 4 seconds. The other notable point is that it allows you to load plugins on demand, which helps reducing the startup time greatly [2] if you happened to use many number of plugins. It also provides some other nice features that pathogen or vundle do not have while still being easy to use. [1]: https://raw.githubusercontent.com/junegunn/i/master/vim-plug/40-in-4.gif https://raw.githubusercontent.com/junegunn/i/master/vim-plug... [2]: http://junegunn.kr/images/vim-startup-time.png http://junegunn.kr/images/vim-startup-time.png
  - nilved 12y ago
    You can do that with pathogen very easily. See my vimfiles repo: https://stealthis.ca/vimfiles.git/tree/bin/update https://stealthis.ca/vimfiles.git/tree/bin/update
gioele 12y ago
> See also pathogen Indeed, vim-plug seems a very nice plugin manager, but it is in no way "more minimalist" than pathogen. How could one be?
- judofyr 12y ago
  Pathogen doesn't manage your plugins. You have to `git clone` (or submodule) and update them yourself.
  - boomlinde 12y ago
    It doesn't do those two things, but I don't think that's a compelling argument for why it doesn't manage plugins. I certainly use it to manage my plugins.
deleted 12y ago
[deleted]
CrystalCuckoo 12y ago
Don't forget neobundle [1], which I find more useful than either as it allows loading for specific filetypes and asynchronous plugin installation. [1] https://github.com/Shougo/neobundle.vim https://github.com/Shougo/neobundle.vim
- coherentpony 12y ago
  One I wasn't aware of. Thanks.

See also pathogen [1] and vundle [2]. [1] https://github.com/tpope/vim-pathogen https://github.com/tpope/vim-pathogen [2] https://github.com/gmarik/Vundle.vim https://github.com/gmarik/Vundle.vim

fndrplayer13 12y ago

Yeah - why should a user switch over from Pathogen or Vundle? I'm not trying to be a jerk -- just suggesting that that explanation is probably worth giving.

phlyingpenguin 12y ago
The biggest reason over Pathogen is automatic installation of your dependent plugins. Biggest reasons over Vundle is parallel downloading, dynamic plugin loading, and static plugins. (all of the reasons for me, YMMV) I've found even that I can install vim-plug with only a few lines of vimscript so that I don't even need to store a .vim directory in my dotfiles repository. Everything can just be installed and run the first time I start vim on a machine, and I can easly :PlugUpdate to get updates to any of my installed plugins.
- saidajigumi 12y ago
  FWIW, this is also quite possible with Vundle. I keep my plugin management in a separate file which also contains the Vundle bootstrap logic for new systems. This stanza sets up Vundle if it isn't already installed...: https://github.com/jwhitley/vimrc/blob/master/.vim/bootstrap/bundles.vim#L7 https://github.com/jwhitley/vimrc/blob/master/.vim/bootstrap... ... and this one after the plugin definitions installs the remaining bundles: https://github.com/jwhitley/vimrc/blob/master/.vim/bootstrap/bundles.vim#L96 https://github.com/jwhitley/vimrc/blob/master/.vim/bootstrap... (I haven't updated this to the new "Plugin" Vundle syntax yet; the change is local but not pushed.) That said, features like vim-plug's postupdate hooks are sweet.
junegunn 12y ago
The most obvious benefit I believe is its ability to update plugins in parallel. A GIF [1] shows that it managed to update 40 plugins in mere 4 seconds. The other notable point is that it allows you to load plugins on demand, which helps reducing the startup time greatly [2] if you happened to use many number of plugins. It also provides some other nice features that pathogen or vundle do not have while still being easy to use. [1]: https://raw.githubusercontent.com/junegunn/i/master/vim-plug/40-in-4.gif https://raw.githubusercontent.com/junegunn/i/master/vim-plug... [2]: http://junegunn.kr/images/vim-startup-time.png http://junegunn.kr/images/vim-startup-time.png
- nilved 12y ago
  You can do that with pathogen very easily. See my vimfiles repo: https://stealthis.ca/vimfiles.git/tree/bin/update https://stealthis.ca/vimfiles.git/tree/bin/update

gioele 12y ago

> See also pathogen Indeed, vim-plug seems a very nice plugin manager, but it is in no way "more minimalist" than pathogen. How could one be?

judofyr 12y ago
Pathogen doesn't manage your plugins. You have to `git clone` (or submodule) and update them yourself.
- boomlinde 12y ago
  It doesn't do those two things, but I don't think that's a compelling argument for why it doesn't manage plugins. I certainly use it to manage my plugins.

deleted 12y ago

[deleted]

CrystalCuckoo 12y ago

Don't forget neobundle [1], which I find more useful than either as it allows loading for specific filetypes and asynchronous plugin installation. [1] https://github.com/Shougo/neobundle.vim https://github.com/Shougo/neobundle.vim

coherentpony 12y ago
One I wasn't aware of. Thanks.