This article is from Svtter's blog, reproduced please retain this information
Vim's Next step
For myself, it is also in this step.
Now that you have a knowledge of vim, HJKL will, F can also be used, ,
may be mapped <leader>
to you, or so on. But I still want to write this blog, to guide the novice (admittedly, also guide themselves). Mislead and don't scold me, please say your point of view.
At this point, I recommend that you map ESC to II and then disable ESC
<Esc><nop><ESC>
In write with VIM (1), I recorded the pattern I used to be more accustomed to ( @+寄存器
), but the regular expression in general, still need to work hard.
Want to use VIM, without GitHub
Probably more people like to find their favorite plugins on http://www.vim.org, but I think it's better to find them on GitHub. Why?
- Because many of the open source projects are already rooted on GitHub, many of the best plugins can be found on GitHub. For example: Nerdtree, youcompeleteme, airline, etc.
- You can tell how good the project is by the number of star on GitHub. Of course, the star is one of the reference standards, to be more precise.
And so on the merits, thought I added.
Use the Plugins Manager to manage your plugins
I personally recommend Vundle
Plug-ins using git update plug-ins, the vimscripts separation, control the different functions of the plug-in can be placed in different locations, to ensure the cleanliness of the VIMRC. This improves the maintenance of personal configuration.
Vundle is the first plug-in, with him, you will find the update plugin, install the new plugin everything is so simple.
The use of Vundle in the readme, but if the English is poor – it doesn't matter, also can read.
The next step of learning
Many people find vimscript difficult to learn, and there is a very good document here. It is accurate to say translation. The translator worked hard.
http://learnvimscriptthehardway.onefloweroneworld.com/
Write with Vim (2)