This post was transferred from: Http://www.cppblog.com/runsisi/archive/2013/04/06/199152.html?
Opt=admin
12 The last day of the year configured the company Rhel vim, the company's network does not agree to upload things and outgoing mail. So sum up to go home and write. There is no environment for Rhel centos or opensuse
graduated almost a year. Although it has been developed under linux windows following encoding, then using git push to Rhel vim configuration similar Ide vc eclipse Linux for so many years. vim :)
Give a in the SECURECRT. The machine hard drive is too small. You can just use a virtual machine to ^^
looks good, color, self-active completion, status bar hints and other functions are very good, for code editing. should be fully enough. It's just a definition of a C/s symbol, a jump in a call relationship, a lookup, and so on or too weak, with Eclipse and source Insight than feeling a notch.
in fact the entire configuration is very easy. The basic use of GitHub on spf13 Daniel's vim configuration is simply to adjust the individual options to suit their environment.
let me introduce my own environment: CentOS 6.3 64bit/opensuse 12.2 64bit, terminal for SECURECRT 7.0, among the SECURECRT terminal emulator options selected by Linux. And tick the two check boxes that follow, and the color styles in the appearance options are black/floral white, for example, as seen in:
Assuming that the gnome-terminal/konsole is used directly, set the background color to the following, for example:
There are two methods of installation:1) Self-active installation mode,2) manual installation mode.
But all require Vim 7.3 python multi_byte--enable-cscope--enable-multibyte--enable-perlinterp=yes--enable-pythoninterp=yes-- Enable-rubyinterp=yes zypper yum and other package Manager installed. Ability to install Vim-enhanced This version number, just centos6.3 rhel6.0 None of the packages are Vim7.3
1) Self-active installation mode
in fact, assuming there is a network, and can use Git to pull the version number from github.com, the configuration process is super simple, because there is a ready-made configuration script on GitHub, you can click on the link to view: Https://github.com/spf13/spf13-vim, let's introduce the configuration process:
1.        using git from https://github.com/spf13/ Spf13-vim.git pull a version number to local;
2. Switch to the local version number working folder. To the folder under the bootstrap.sh to join the operational permissions;
3. Run the script just now. Just need to wait for the good, will take the initiative to download other vim plug-ins.
4. then change the ~/.VIMRC or create a new ~/.vimrc.local, add the following sentence, the terminal color is set to the color :set t_co= so you can.
2) manual installation mode
Suppose the network environment does not support git . Everything needs to be installed manually. Manual mode installation is cumbersome. In fact , it is the operation of the spf13-vim/bootstrap.sh script.
1.        interview Https://github.com/spf13/spf13-vim Click "Zip" button, packaged to download the plugin. And unzip the
2.        spf13-vim/bootstrap.sh The operation of the file, the original vim configuration file backup. Then link the new profile to ~/ folder
3. manually download the Https://github.com/gmarik/vundle plugin. Unzip and remove the last "-master" from the directory nameand copy the directory to the ~/.vim/bundle directory, without which the new
4. ChangesSpf13-vim/.vimrc.bundlesfile. Similar in this configuration fileBundle ' xxx/yyy 'the line is actuallyGitHubon the oneVimThe plug-in path. AsBundle ' Gmarik/vundle 'of theUrlPath isHttps://github.com/gmarik/vundle. Direct ChangesLet G:spf13_bundle_groupsThe ability to remove some unwanted plug-in groups, each plug-in group contains plug-ins are defined in the configuration file below. If you do not want to remove the entire plug-in group, you can delete some unnecessary plugins at the definition of the plug-in group, but note that at the beginning of the configuration file,"Deps"it is necessary to stare at the following plugins, which cannot be erased .
5.        then manually download these plugins, unzip. Remove the end of the directory name "-master" ~/.vim/bundle/ below
6. finally install according to the spf13-vim/bootstrap.sh final installation command, you can
7. In accordance with the above self-active mode of article 4 , add a terminal color configuration can be.
/files/runsisi/vim simple configuration. pdf
Vim Configuration Summary