diff options
author | cos <cos> | 2020-04-20 19:46:39 +0200 |
---|---|---|
committer | cos <cos> | 2020-04-20 19:46:42 +0200 |
commit | feeb29e477dd50236e0e86e9d0634752d06b0b34 (patch) | |
tree | 95c696d4006994ebfc14a913c9fe21fc3df28040 | |
parent | b28c923979d08336abe31c403b5f7c2757e02f31 (diff) | |
download | vdebug-cr/pathogen-infect.zip |
Improve pathogen install instructionscr/pathogen-infect
New phrasing mentions both of the commands required for pathogen to pick
up vdebug in an empty vimrc.
-rw-r--r-- | README.md | 5 |
1 files changed, 3 insertions, 2 deletions
@@ -32,8 +32,9 @@ The actual installation is no different than for any other Vim plugin, you can * install manually: Clone or download a tarball of the plugin and move its content in your `~/.vim/` directory. You should call `:helptags ~/.vim/doc` to generate the necessary help tags afterwards. -* use Pathogen: Clone this repository to your `~/.vim/bundle` directory and - `:call pathogen#helptags()` afterwards. +* use Pathogen: Clone this repository to your `~/.vim/bundle` directory, run + `:execute pathogen#infect()` and `:call pathogen#helptags()` afterwards. + * use your favorite plugin manager: Put the respective instruction in your init file and update your plugins afterwards. For Vundle this would be `Plugin 'vim-vdebug/vdebug'` and `:PluginInstall`. |