Skip to content
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

Add background to StatusLineNC when termguicolors is disabled #28796

Closed
stepanbujnak opened this issue May 17, 2024 · 5 comments · Fixed by #28810
Closed

Add background to StatusLineNC when termguicolors is disabled #28796

stepanbujnak opened this issue May 17, 2024 · 5 comments · Fixed by #28810
Labels
defaults issues or PRs involving changing the defaults enhancement feature request highlight

Comments

@stepanbujnak
Copy link

Problem

Screenshot 2024-05-17 at 02 19 46

Above is a screenshot of neovim 0.10.0 running inside Terminal.app on macOS which doesn't support true colors with two windows (vertical split). Since there's no background color for the top window status bar, it makes it hard to distinguish where the top window ends and bottom window begins, especially when there's a lot of text.

Expected behavior

Would it be possible to add a background color to the window status bar? Thank you.

@stepanbujnak stepanbujnak added the enhancement feature request label May 17, 2024
@zeertzjq zeertzjq changed the title Add background to vertically split windows when termguicolors is disabled Add background to StatusLineNC when termguicolors is disabled May 17, 2024
@echasnovski
Copy link
Member

The problem for default color scheme with 'notermguicolors' is that there is no good (robust and visually accessible) way to highlight non-active statusline to be distinguishable both from text and active statusline. The best compromise in my opinion is already present and it uses bold text in non-active statusline.

I'd suggest that the solution here is for users to adjust StatusLineNC to fit their taste. For example: hi StatusLineNC cterm=bold,underline (underline is used very sparingly due to not having good universal support) or hi StatusLineNC ctermfg=12 (to highlight with different color).

@justinmk
Copy link
Member

For non-truecolor, I think we should consider underline for the StatusLineNC. I can accept the arguments against it for truecolor, but not for 256 color case.

@justinmk justinmk added the defaults issues or PRs involving changing the defaults label May 17, 2024
@echasnovski
Copy link
Member

For non-truecolor, I think we should consider underline for the StatusLineNC. I can accept the arguments against it for truecolor, but not for 256 color case.

Using cterm=underline is not a problem for me as far as aesthetic goes ('notermguicolors' case is more like "make as good as is reasonable" for me).

The main concern was that if terminal emulator does not support 'termguicolors' then it might as well not support underline.

So I guess the question is should it be cterm=bold,underline (more visible than necessary but safer for compatibility) or just cterm=underline (less noisy but less compatible)?

@justinmk
Copy link
Member

So I guess the question is should it be cterm=bold,underline (more visible than necessary but safer for compatibility) or just cterm=underline (less noisy but less compatible)?

Either is fine with me. Underline is a big help. IMO bold is not visually helpful so it makes no difference (though "bold" in ANSI colors can actually mean a different color).

@echasnovski
Copy link
Member

Either is fine with me. Underline is a big help. IMO bold is not visually helpful so it makes no difference (though "bold" in ANSI colors can actually mean a different color).

OK, bold,underline it is then.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
defaults issues or PRs involving changing the defaults enhancement feature request highlight
Projects
None yet
Development

Successfully merging a pull request may close this issue.

4 participants