-
-
Notifications
You must be signed in to change notification settings - Fork 96
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
Scope underline highlight is different from the char highlight. #686
Comments
This is a limitation with your terminal. Not all terminals support underline with a different color. |
Which terminals are supported? Because I tried with both Kitty and iTerm2 (EXTREMELY popular terminals), and the above commenter tried with Alacritty and all of them behave as this issue described. This issue should not be closed. If it's intended behaviour then this should be flagged a feature request instead, because supporting iTerm2/Alacritty/Kitty seems very basic. |
Kitty at least should work, that's what I use. Tmux might mess with things, too. If you use tmux, try to add this in your tmux config.
There is nothing I can do about this. I just set the highlight group. If it doesn't work, it's not supported by your terminal, or your terminal is configured wrong. |
You're right!!! It IS tmux that's messing with it. If i go to a file without tmux the underline works correctly. |
There just was a discussion about this on Reddit as well, maybe something there works for you. |
In case anyone comes across this later - I managed to fix it by adding this to my tmux.conf (I'm using kitty):
|
In case anyone using alacritty with tmux, try at this to your tmux config. It fixed for me. |
This worked for me but I had also had to upgrade Alacritty from version 10 to 12. |
I have the same problem as you. I'm using wezterm.According this document, This config can fix this problem.
OR Add below config to if [[ $TMUX != "" ]] then
export TERM="tmux-256color"
else
# export TERM="xterm-256color"
export TERM="wezterm"
fi
|
I have the same problem. My setup is:
Like above, I've added the line If I understand @lukas-reineke correctly, the only point where it can come from by now is the color scheme, right?!? Does anybody has a hint for me, what the highlighting can be to discard the horizontal underlining (or set the color of it)? I've tried some (Line number included) but nothing has worked so far. The vertical indents are working and are awesome with changing the color depending on the scope :) |
No, this is not even related to Neovim. It is a problem with your terminal / tmux and how they are configured.
If you just don't want to display the underlines at all, you can turn off |
@lukas-reineke -> super cool: scope = {
enabled = true, -- 'true': Highlight only the intended indentation and the current scope by an underline.
show_start = false, -- Shows an underline on the first line of the scope.
show_end = false, -- Shows an underline on the last line of the scope.
show_exact_scope = false,
injected_languages = true,
}, Made my day <3 ...happy Karneval if you are one of those Karneval-people in Germany :-P |
does iterm2 support this feature? |
it seem the iterm2 and wezterm don't support this feature defaultly. |
Yes, see https://wezfurlong.org/wezterm/faq.html?h=underline#how-do-i-enable-undercurl-curly-underlines (It's the same issue) -- in short you need the custom terminfo file and to set |
Problem
I'm using Alacritty with Tmux with onedarkpro theme.
The scope underline highlight is not the same as the highlight, using it with rainbow-delimeter.nvim.
![image](https://private-user-images.githubusercontent.com/69962410/272358408-b279577e-d4f0-4579-aba7-72b97839e4a4.png?jwt=eyJhbGciOiJIUzI1NiIsInR5cCI6IkpXVCJ9.eyJpc3MiOiJnaXRodWIuY29tIiwiYXVkIjoicmF3LmdpdGh1YnVzZXJjb250ZW50LmNvbSIsImtleSI6ImtleTUiLCJleHAiOjE3MTg0MzgzNTgsIm5iZiI6MTcxODQzODA1OCwicGF0aCI6Ii82OTk2MjQxMC8yNzIzNTg0MDgtYjI3OTU3N2UtZDRmMC00NTc5LWFiYTctNzJiOTc4MzllNGE0LnBuZz9YLUFtei1BbGdvcml0aG09QVdTNC1ITUFDLVNIQTI1NiZYLUFtei1DcmVkZW50aWFsPUFLSUFWQ09EWUxTQTUzUFFLNFpBJTJGMjAyNDA2MTUlMkZ1cy1lYXN0LTElMkZzMyUyRmF3czRfcmVxdWVzdCZYLUFtei1EYXRlPTIwMjQwNjE1VDA3NTQxOFomWC1BbXotRXhwaXJlcz0zMDAmWC1BbXotU2lnbmF0dXJlPWQ3MzRiNDRiODQ1M2YzMGI4ZjQ1NDM4ZWQ1Mjk1NTI0ZjA0NzU2NDdlNTc4M2Y0ZGZhN2NhMjk4YzY4M2RlNzEmWC1BbXotU2lnbmVkSGVhZGVycz1ob3N0JmFjdG9yX2lkPTAma2V5X2lkPTAmcmVwb19pZD0wIn0.68JEnYkqKeX73c2ek4Os0EZS5apscA13CGeahvpgYXo)
![image](https://private-user-images.githubusercontent.com/69962410/272358487-5c14dc3f-b477-4bad-b1bb-2c5e56155c55.png?jwt=eyJhbGciOiJIUzI1NiIsInR5cCI6IkpXVCJ9.eyJpc3MiOiJnaXRodWIuY29tIiwiYXVkIjoicmF3LmdpdGh1YnVzZXJjb250ZW50LmNvbSIsImtleSI6ImtleTUiLCJleHAiOjE3MTg0MzgzNTgsIm5iZiI6MTcxODQzODA1OCwicGF0aCI6Ii82OTk2MjQxMC8yNzIzNTg0ODctNWMxNGRjM2YtYjQ3Ny00YmFkLWIxYmItMmM1ZTU2MTU1YzU1LnBuZz9YLUFtei1BbGdvcml0aG09QVdTNC1ITUFDLVNIQTI1NiZYLUFtei1DcmVkZW50aWFsPUFLSUFWQ09EWUxTQTUzUFFLNFpBJTJGMjAyNDA2MTUlMkZ1cy1lYXN0LTElMkZzMyUyRmF3czRfcmVxdWVzdCZYLUFtei1EYXRlPTIwMjQwNjE1VDA3NTQxOFomWC1BbXotRXhwaXJlcz0zMDAmWC1BbXotU2lnbmF0dXJlPWE0MDMxMWY3MmI4M2JlYjkwMGRlODVmMGZhMTI4M2Q3ZjZlM2YzNzIwOTc5MzdhNmU5NjBmMDVlNmVjNDc1MmYmWC1BbXotU2lnbmVkSGVhZGVycz1ob3N0JmFjdG9yX2lkPTAma2V5X2lkPTAmcmVwb19pZD0wIn0.kaamSHo0whHadlwMpr19jR8z9DO5n2PuaW_RgFxskuI)
Steps to reproduce
ibl config
onedarkpro config
Expected behavior
Highlight to be the same.
Neovim version (nvim -v)
0.9.2
The text was updated successfully, but these errors were encountered: