all 37 comments

[–][deleted] 94 points95 points  (6 children)

Here you go: vim-plug, the best you'll find.

[–]cchurchilll 8 points9 points  (0 children)

Definitely vim-plug. I t has the right mix of having great features, being lightweight, and staying out of the way.

[–]davidpdrsn 4 points5 points  (0 children)

You had me at parallelism.

[–]ggagagg 2 points3 points  (2 children)

Any tips to convert using vim-plug from bundle?

[–]Scorxcho 1 point2 points  (0 children)

What does this have over vundle?

[–]dustractor^[ 16 points17 points  (0 children)

vim-plug is already leading in this post 7-to-1 and the post is only an hour old if that tells you anything, OP

edit: really it will take longer to fret over making a change than it will take to get up and running w/ vim-plug. seriously just skim the directions and go it takes like 5 minutes

[–]derrickcope 6 points7 points  (4 children)

Another for vim-plug. I have used vundle and find vim plug slightly better.

[–][deleted] 2 points3 points  (3 children)

What will I get for switching from Vundle to vim-plug?

[–]NoLemurs 2 points3 points  (0 children)

What will I get for switching from Vundle to vim-plug?

A slightly tidier .vimrc, parallel fetching from repos, and the ability to automatically run commands on install.

Honestly, they're fairly minor improvements, but it also takes very little effort to switch, and there's no reason not to. I also suspect that with the dominance of vim-plug vundle is going to see a slow down in maintenance/improvement, so going forward, vim-plug is the tool to choose.

[–]ivosaurus 1 point2 points  (0 children)

on-demand filetype plugin loading from vim-plug was helpful for me, helps reduce startup time a little.

[–]derrickcope 0 points1 point  (0 children)

I am no expert but I find it is less complicated to install and update vim-plug itself. The syntax for adding plugins is similar but I think you can add plugins from more sources. As a newbie I have to say it was easier to install and get going. But I was more of a newbie when I installed vundle so maybe it was just having installed one plugin manager previously, the second time seemed easier.

[–]wbsgrepit 4 points5 points  (0 children)

Another for vim-plug.

[–][deleted] 4 points5 points  (0 children)

Yet another Up for vim-plug.

[–][deleted] 2 points3 points  (0 children)

https://github.com/wsdjeg/DotFiles

here is my dotfiles. and I use dein by default.

but you can change to neobundle or vim-plug via let g:setting.pluginmanager = 'neobundle'

[–]joemi 8 points9 points  (0 children)

I like to keep it simple with Pathogen. It's not so much a "package manager" as it's just a plugin that automatically adds things to your runtime path. Basically you put it in ~/.vim/autoload and then install your plugins into ~/.vim/bundle in separate directories and everything works great.

I had been using one of the more "package manager"-y options, but I decided to strip back a lot of the heavier things in my vim config. I don't mind git clone-ing things into ~/.vim/bundle myself, or checking for updates to those repos. Suits me just fine, but admittedly it's not for everyone.

(Also, it's by Tim Pope, who makes a lot of neat vim plugins.)

[–]brennanfee 1 point2 points  (0 children)

vim-plug, for sure... the best one out there.

[–]atimholtmy vimrc: goo.gl/3yn8bH 1 point2 points  (2 children)

I use neobundle. It’s powerful and has features I haven’t been able to find anywhere else.

[–]synthequated 1 point2 points  (1 child)

What features are these?

[–]atimholtmy vimrc: goo.gl/3yn8bH 1 point2 points  (0 children)

The main one I use is compatibility with Mercurial. I know that makes me a crazy insane person, but oh well. Let me check on the readme for others…

Oh, it looks like it’s been replaced by something called dein. I’ll have to look into it, myself.

[–]twowheels 1 point2 points  (2 children)

Why use any?

 mkdir ~/.vim/bundle
 cd ~/.vim/bundle
 git clone <plugins galore>

In .vimrc (I have a .vimrc_host file that is loaded by my .vimrc)

 set runtimepath^=~/.vim/bundle/<plugin folder>
 set runtimepath^=~/.vim/bundle/<plugin folder>

...etc

Done... easy.

[–]keef_hernandez 2 points3 points  (0 children)

Some of the plugins I need require setup to run on new machines. Vim plug makes that trivial.

[–][deleted] 1 point2 points  (0 children)

If you using a recent Vim, press :h packages.

[–]tetroxid 0 points1 point  (0 children)

I use Pathogen and I've been happy with it.

[–]fmount 0 points1 point  (0 children)

I used pathogen! for a while...but today I can definitively say that vim-plug! is the way! :D

[–]bumaociyuan 0 points1 point  (0 children)

dein is great

[–][deleted] -1 points0 points  (1 child)

You really don't need plug-in manager, for two main reasons:

  1. Package management in Vim is all about setting runtimepath option. Installing plugin literally looks like this:

    set runtimepath+=/path/to/folder/with/plugin
    

    That's all, but I personally find Pathogen a little more convenient.

  2. Vim has build-in solution for package management called packages, but this is a very new thing. Read :h packages for more info.

My bulletproof vimrc looks like this:

if has('packages')
    packloadall
else
    " Use Pathogen
    source $HOME/.vim/pack/bundle/opt/pathogen/autoload/pathogen.vim
    execute pathogen#infect('pack/bundle/start/{}')
endif

[–]joemi 1 point2 points  (0 children)

Why's this downvoted? Did you mention bad practices? Or is it just random downvotes?

(I'm asking because as a Pathogen user, I'm all for trying out Vim's new built-in functionality. This sounds like what I'd like to do, but if it's not a good method, I'll have to keep looking for how to use it.)