Believe that the code farmers have heard two great artifacts, one is Emacs, one is vim. Everyone knows that e party and V party are always arguing. In fact, this is not a good argument, but everyone has their own application of things. The author touches vim and also touches Emacs. For authors, Vim is more appropriate.
Below, let us introduce the author's own vim configuration. GitHub Address: https://github.com/tenghui0425/VimScripts
First of all, let's look at the big picture. This is the VIMRC configuration of the diagram directory situation.
The configuration is mainly the following blocks.
- Basic configuration, placed under the. VIMRC, such as a global map. Finally, load a basic configuration file Load_vimrc.vim file.
- Plug - ins. The author uses the Vundle plugin to manage plugins. Management plug-ins have a lot of, for the base of his, the author has not been used, has been fond of vundle, it can manage all the GIT data, to update and so on. Very convenient to use. Do not know how to use, I believe, Vundle's readme everyone can understand, to a portal. Https://github.com/gmarik/Vundle.vim
- Encapsulation plug-in management. If you use heap a lot of plug-ins under the. VIMRC configuration, I believe you will be uncomfortable to see, especially the "neat" program ape. Of course, the author is also a "neat" program ape, so the management of the plug-in more than a layer of encapsulation. The following is an introduction to how to achieve.
All packages are in Load_vimrcs.vim, and after loading this file, the final
Loadvimrcs function, this function will go to load all the plugins. What about the loading process?
It is necessary to load the Vundle first.Then load all the. vimrc suffix files under the Vimrcs directory, and then use Vundle to load the. vimrc file. Of course, in order to use the configuration better, I used the Pluginadd command to redefine the vundle.
In this way, all plug-in configurations are separate and look much fresher. However, this can be a lot of files. Of course, these can be merged, so if you see the file more uncomfortable, you can also combine the contents of multiple files a file.
So what to add plug-ins later? Create a new file under Vimrcs. vimrc as a suffix, preferably with the name of the plug-in as a filename, to facilitate later search. Then use Pluginadd to add the name of the plugin in front of the file. Next you can write a variety of configuration content. Last save use the Bundleinstall command to install the plugin.
Here are a few of the authors are very popular plug-ins, because the author is basically C + + development, so the basic C + + plug-in. As follows:A.vim: Switch between the header file and the source file.C.vim: Very good, very powerful, must be installed. Automatically insert comments, compile, etc.Grep.vim: Enhanced grep.
MINIBUFEXPL: Open the file like the Base Editor tag page.Supertab: Auto-complete.
Unite: Find files.
Vim-expand-region: Check the contents of the quotation marks and parentheses.
Vim-multiple-cursors: Edit multiple places at the same time.
Nerdtree: Directory tree. The left side of the first big picture.Tagbar:tag tags, function names, and so on. The right side of the first big picture.
The use of each plug-in, you can refer to their readme.
Compiler of God vim big makeover
