Clever Geek Handbook

Why Fugitive: Gdiff explodes in colors and doesn't do anything useful?

I just installed fugitive and it works very nicely. There seems to be something wrong with :Gdiff

, although perhaps due to an incompatible setting somewhere I hope you can help me identify. When I run the command, the colors on the screen just go crazy and nothing useful happens as far as I can tell, such as highlighting the changed lines.

Any clue what might be the problem or where should I look first?

I am using Gvim x64 for Windows. Here is the outputgvim.exe --version

and here is a list of my installed packages:

SingleCompile
l9
nerdcommenter
nerdtree
pathogen
pylint
smooth_scroll
snipmate
supertab
surround
vim-fugitive
vim-indent-guides
vim-powerline
vim-scriptease

Screenshots

This is what a normal window looks like in gvim.exe with my configuration:

Before gdiff

This is how it looks when I :Gdiff

(no changes in the file):

After Gdiff (no changes)

And this is how it looks when I am :Gdiff

and the file has an unset change. (I added 2 lines above line 13).

After Gdiff (with changes)

+3


source to share


2 answers


It seems to me that your diff program is performing very poorly. What does he say :set diffexpr?

?



To isolate the problem, I would get a git and a cursory from the image. Just make two copies of the file and then, by editing foo.py,:diffsplit bar.py

+1


source


Try adjusting the color in the following highlight variable



hi! DiffAdd      guibg=#003300
hi! DiffChange   guibg=#003300
hi! DiffDelete   guifg=#330000 guibg=#330000
hi! DiffText     guibg=#990000
0


source






More articles:


All Articles