Red Hat Bugzilla – Bug 204042
vimdiff wrong color commented strings
Last modified: 2007-11-30 17:11:41 EST
Description of problem:
Creating 1.txt and 2.txt.
Check it by: $ vimdiff 1.txt 2.txt
I see only blue background between 12345 and 54321 in 2.txt file.
Version-Release number of selected component (if applicable):
gvimdiff 1.txt 2.txt
show this fine for me.
vim -d shows this bug, gvim doesn't.
temporary fix until the new package is on the mirrors is
:hi Comment cterm=NONE ctermfg=DarkRed gui=NONE guifg=red2
The resolution to this bug changes gvim color display for me. Using the default
color scheme, comment lines used to be in blue and numerics were in red (at
least for fortran files) since i've been using gvim.
Can this be reverted, please? It's difficult getting used to this change
(really, it's only been a few hours of use ;)
This still wrong here:
$ cat 11.txt
test --test ewewe
$ cat 22.txt
test --test test
$vimdiff 11.txt 22.txt
Ping. Why not please drop the vim-7.0-syncolor.patch, since it does not seem to
even solve the original issue here. Thanks
I see you're not too keen on reverting the change you made to vim based on this
bug, but can you please advise on something I can put in my vimrc to allow the
old behaviour. Thank you.
I've built vim-7.0.109-1 which should solve those issues. It changes the colors of
added lines in diff mode instead of the colors of all comments.
I'm not sure if this will make it into FC6, grab the packages from rawhide instead.
vim-7.0.109-1 has not appeared in rawhide yet, maybe because we're FC6 release
mode. I hope it can make it into FC6, at least as an update.