New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Poor readability in vimdiff with cursorline #40
Comments
Hmm, that's weird. Is this iterm? Could your reproduce that without vimdiff? And if this is iterm, what's your |
Yeah, I'm using iTerm2. I am using the default 256
Unfortunately, I cannot reproduce this issue without vimdiff, since the issue only occurs the highlighted green/orange lines created by vimdiff. Gruvbox + cursorline works just fine on regular lines. |
I'm pretty sure that's not causing this issue, but you'd better change |
If it helps anyone, I've come up with a workaround that disables cursorline in vimdiff mode. I added the following to my vimrc:
|
See this issue for more information: morhetz/gruvbox#40
+1 having the exact same Problem w/ xfce4-terminal. imho, the lightish gray, that is normally a perfect cursorline color, has very poor contrast to fg/text color (black?) when vimdiffing. |
@ikcalB I'm sorry, I can't reproduce it with xfce4-terminal 0.6.3 vim from *buntu lts 14.04: |
Debian Jessie (testing)
I could upload another screenshot (which would look almost identical to the above) |
@ikcalB |
@morhetz
|
@AndroidOatmeal, @ikcalB: |
@morhetz Thank you for your effort! Now, the cursorline is "behind" the highlighting of the diff - it seems to vanish. Can you think of a good possibility, to have a cursorline with good visibility in diff mode? |
@ikcalB That's how it currently works as I suppose that fixes issue Is highlighted line number not enough to distinguish current line? |
Hello,
I've noticed that when I have
:set cursorline
in my vimrc and I try to vimdiff something, my cursor line makes diffed text quite hard to read. See picture for an example.Any ideas on how to solve this?
The text was updated successfully, but these errors were encountered: