[Tools] Vim Plugin Management

When we use plug-ins, we do not want the plug-in installation is very messy, it is not an invisible black box, but also for the next convenient installation in other places.

Due to the convenience of plug-in management, so there are vundle, the following to do some introduction:

1. A plug-in manager, itself is also a plug-in, which is required tools:

git clone https://github.com/vundlevim/vundle.vim.git ~/.vim/bundle/vundle.vim

2. Vundle manages other plugins in. VIMRC with the following configuration items:

"##################################/Vundle.vim ###################################"Https://github.com/VundleVim/Vundle.vimSet Nocompatible"Be improved, requiredFileType off"Required"set the runtime path to include Vundle and initializeSet rtp+=~/.vim/bundle/vundle.vimcall vundle#begin ()"Alternatively, pass a path where vundle should install plugins"Call vundle#begin (' ~/some/path/here ')"Let Vundle manage Vundle, requiredPlugin'Vundlevim/vundle.vim' "plugin management, required"The following is examples of different formats supported."Keep Plugin commands between vundle#begin/end."plugin on GitHub repo"Plugin ' tpope/vim-fugitive 'Plugin'Scrooloose/nerdtree' "directory tree, Https://github.com/scrooloose/nerdtree/blob/master/doc/NERD_tree.txt"plugin from http://vim-scripts.org/vim/scripts.htmlPlugin'L9'"Git plugin not hosted on GitHub"Plugin ' Git://git.wincent.com/command-t.git '"git repos on your local machine (i.e. when working on your own plugin)"Plugin ' File:///home/gmarik/path/to/plugin '"The sparkup vim script is in a subdirectory of this repo called Vim."Pass The path to set the Runtimepath properly.Plugin'Rstacruz/sparkup', {'RTP':'vim/'}"Install L9 and avoid a naming conflict if you ' ve already installed a"different version somewhere else."Plugin ' Ascenator/l9 ', {' name ': ' NewL9 '}"All of your Plugins must is added before the following lineCall Vundle#end ()"RequiredFileType plugin indent on"Required"to ignore plugin indent changes, instead use:"filetype plugin on""Brief Help":P luginlist-lists configured plugins":P lugininstall-installs plugins, append '! ' to update or just:P luginupdate":P luginsearch foo-searches for foo, append '! ' to refresh local cache":P luginclean-confirms removal of unused plugins; Append '! ' to auto-approve removal""see:h Vundle For more details or wiki for FAQ"Put your non-plugin stuff after this line"##################################/Vundle.vim ###################################"Map Ctrl + V to: nerdtreetoggle+ carriage returnMap <C-V>:nerdtreetoggle<cr>

The configuration meaning and general commands are clearly written in the comments above and it is necessary to take a closer look.

3. The terminal input vim opens the blank page, uses the:P Lugininstall installs the configuration the plug-in, if needs to uninstall, first the plug-in name comments out, uses:P Luginclean to unload.

Here are just a few introductions, the configured files are here: Https://github.com/farwish/vimrc.git, the. VIMRC in the directory is overwritten by the current user, and then installed.

Learn this way of configuration, find some powerful plug-ins, you may not need the IDE.

@ Black eyed poet <farwish.com>

Link:http://www.cnblogs.com/farwish/p/5792884.html

[Tools] Vim Plugin Management