Tutorial by Examples

A plugin could present itself as a single file containing 30 lines of vimscript or as 20MB of vimscript/python/ruby/whatever split into many files across a dozen of directories that depends on a number of external tools. The former is obviously easy to install and manage but the latter could pause ...

Single file plugin Put the file under $HOME/.vim/plugin or $HOME/vimfiles/plugin This would source the plugin on startup of Vim. Now the user could use everything defined in it. If the plugin however needs activation, the user either has to execute the command themselves whenever they want to use...

https://github.com/MarcWeber/vim-addon-manager

Vundle is a plugin manager for Vim. Installing Vundle (Full installation details can be found in the Vundle Quick Start) Install Git and clone Vundle into ~/.vim/bundle/Vundle.vim. Configure plugins by adding the following to the top of your .vimrc, adding or removing plugins as necessar...

See :help packages.

vim-pathogen is a runtimepath manager created by Tim Pope to make it easy to install plugins and runtime files in their own private directories. Installing Pathogen Put pathogen in ~/.vim/bundle (here with Git, but it's not mandatory): git clone https://github.com/tpope/vim-pathogen.git ...