update README markdown syntax
This commit is contained in:
parent
b8ec60d317
commit
74580f299d
1 changed files with 5 additions and 1 deletions
|
@ -313,15 +313,19 @@ You can also add your own favorite script from [vim-scripts.org](http://vim-scri
|
|||
|
||||
## Use git and pathogen to manage vim plugins
|
||||
As amix mentioned, you can isntall your own plugins via pathogen,for instance vim-rails:
|
||||
|
||||
cd ~/.vim_runtime
|
||||
git clone git://github.com/tpope/vim-rails.git sources_plugins/vim-rails
|
||||
|
||||
After this,you got vim-rails under sources_plugins/vim-rails as a git local repo.
|
||||
**But** maybe amix forgot to mention that you have to change plugins_config.vim under ~/.vim_runtime/vimrcs to make the plugin work.
|
||||
**But** maybe amix forgot to mention that you have to change plugins_config.vim under ~/.vim_runtime/vimrcs to make the plugin work.
|
||||
Just to add a line to plugins_config.vim and it may look like this:
|
||||
|
||||
call pathogen#infect('~/.vim_runtime/sources_forked')
|
||||
call pathogen#infect('~/.vim_runtime/sources_non_forked')
|
||||
**call pathogen#infect('~/.vim_runtime/sources_plugins')**
|
||||
call pathogen#helptags()
|
||||
|
||||
The line **bold** is added. Then pathogen will get everything done.
|
||||
|
||||
**Note:** I don't use subtree or submodule to manage vim plugins at this time, so you'd better know what you are doing with your plugins.
|
||||
|
|
Loading…
Reference in a new issue