Why won't vim recognise a plugin command in the vimrc, but it will recognise it when running?

Question

I've installed the vim-gitgutter plugin with pathogen. I can type :GitGutterLineHighlightsEnable from inside vim and line highlights are turned on, great.

But I want line highlights to be automatically enabled at startup, so I added the command to my ~/.vimrc. However when I start vim, I get "E492: Not an editor command: GitGutterLineHighlightsEnable". Once vim has started up, I can run the command.

My vimrc looks like this:

execute pathogen#infect()
colorscheme railscasts

  .. snip tabs and colors etc ..

GitGutterLineHighlightsEnable
hi GitGutterAddLine guibg=#222F22
hi GitGutterChangeLine guibg=#222239
hi GitGutterDeleteLine guibg=#2F2222

score 9 · Answer 1 · edited May 23 '17 at 12:16

9

Figured it out.

.vimrc is executed before plugins are loaded. From this related question, I changed the commands to:

autocmd VimEnter * GitGutterLineHighlightsEnable

This executes the command after vim has started up.

edited May 23 '17 at 12:16

Community

1
1

answered Jan 24 '14 at 01:14

Jordan

2,281
1
17
24

score 7 · Answer 2 · answered Jan 24 '14 at 01:22

7

Use

let g:gitgutter_highlight_lines = 1

instead of

GitGutterLineHighlightsEnable

answered Jan 24 '14 at 01:22

rolnn

928
9
16

score 6 · Accepted Answer · answered Jan 24 '14 at 05:03

6

As you determined yourself, plugins are processed after the .vimrc.

What you can do if you don't like using a VimEnter autocmd, is put a file in your ~/.vim/after/plugin directory for any commands that should run after plugins are loaded.

answered Jan 24 '14 at 05:03

Ben

8,725
1
30
48

Why won't vim recognise a plugin command in the vimrc, but it will recognise it when running?

3 Answers3