Earlier this week I wrote Beginner's Guide to Unite, which was an attempt to demystify the popular Unite plugin. I noticed people grumbling on Reddit that it didn't contain any installation instructions.
I've written a little bit about working with plugin managers before:
The Windows-specific post came out of a series of articles on Windows and Vim. So, what are plugin managers, why are they needed, and how are plugins installed?
Installing Vim Plugins
One does not simply walk into Mordor and install a Vim plugin. The thing about plugins is they're usually bundles of lots of different subdirectories that Vim expects to be copied to the correct place. Plugins can consist of plugin files, which go in
~/.vim/plugin, syntax files which go in
~/.vim/syntax, autoload files which go in... you get the idea. Plugins have multiple files and directories and installing them is a giant pain.
You're probably thinking: "but that sucks, I just want to quickly try out a plugin to see what it does! I don't want to mess up
~/.vim all the time!"
Exactly, and that's why plugin managers were created.
All plugin managers really do is manipulate
'runtimepath'. I've written about this before in Vim 101: runtimepath, so go there to read about what exactly that means.
If you sync your dotfiles with Git and don't mind messing around with submodules, check out Pathogen, otherwise get Vundle. Both have excellent documentation and are easier to learn than manually copying files to
I'm not going to teach you how to use Vundle or Pathogen here -- read their documentation on GitHub and try them out. I've used both of them a lot since they were released... they definitely help me out writing and researching material for this blog!