What are the differences between Vundle and NeoBundle?

Question

I would like to have a nice and easy way to manage vim plugins. I found NeoBundle and Vundle . What are the main differences between the two? I know NeoBundle is a Vundle plug, but what makes it different?

What are you using?

Answer 1

Here 's an article written (in Japanese) by NeoBundle Shougo on why he wrote NeoBundle and how NeoBundle differs from Vundle .

Actually, NeoBundle is fork Vundle . Shougo added some features to the Vundle plug, but recently found that he could not follow the upstream development of the Vundle , so he turned the plug into a new plugin, now called NeoBundle .

The differences are described below:

• Rename teams from Vundle , replace Bundle with NeoBundle . (Example: BundelInstall to NeoBundleInstall ).
• Add support for vital.vim , a vim utility library written by thinca .
• NeoBundle works even if you set the shellslash parameter to a different one than the standard one.
• Add support for vimproc , a startup plugin written by Shougo.
• Add an interface for unite.vim written by Shogo, he also marks it as the main motive for writing NeoBundle .
• Add support for plugins hosted as a Subversion / Mercurial repository, but it is still an experimental feature.
• ( UPDATED ) Now NeoBundle adds a lazy boot function where Vundle hasn't. It allows you to load plugins at a user-defined point in time, and not just during vim initialization, where .vimrc loaded.

I use Vundle because I have enough of my needs (I used a pathogen before). But you can try NeoBundle .

---

( UPDATE ) NeoBundle now stopped active development and will be replaced by dein.vim , which is Shougo another new plugin manager. As an additional note, you can also take a look at the vim-plug that I am currently using.