-
Notifications
You must be signed in to change notification settings - Fork 52
feature: Improve background colors of signs highlight groups #58
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
Comments
SignColumn
highlight group for signs or provide a way to configure sign highlights
Thanks for bringing this up, that is definitely unexpected. The signs added by this plugin don't add a background highlight group. In the case of code we use only the highlight group returned from the icon provider. So in the case of Then in the case of headings we use only the value of the foreground highlight group: https://github.com/MeanderingProgrammer/markdown.nvim/blob/main/lua/render-markdown/handler/markdown.lua#L37-L59 In both of these cases we do not add I've played around with a few other color schemes and am unable to replicate the background being different, though I can clearly see it in your screenshot. What colorscheme do you use? |
I use my own theme, which I generate with this lua tool. For the icons I'm using mini.icons, which has highlight groups with only a foreground color defined. Also there's no such thing really as background and foreground highlight groups. Highlight groups can have both a foreground and background color. If you'd want to make sure to only use the foreground color of an existing highlight, you'd need to extract that from the highlight group. |
Yeah, I call them Which icon provider are you using? If it's If it's I'm just rather lost on how a background is getting set on these icons for you. Is there some fallback logic happening somewhere? As far as I'm aware the solution |
I just looked through my tool again and tested a bit: Signs highlight groups do not behave different from other highlight groups. Anything that's not specified for a highlight group falls back to what's specified for |
Ah, I was wondering why I wasn't able to get something to display this behavior. Turns out that most color schemes use the same background color for |
…d by buftype # Details Request: #58 Not all color schemes use the Normal background color for the sign column. This can lead to some not so great looking icons. Fix this by combining the color we were going to set with the SignColumn background. Add a new configuration section 'sign' where this is defined and moifiable. While we are adding a new section for signs add 2 other abilities. - The ability to globally disable them from components that create them - The ability to disable them within a set of buftypes, use a default value of 'nofile' so that signs do not appear in LSP documentation
Added the logic to use the SignColumn background here: d398f3e Please update and lmk if it looks better! Also added the ability to disable signs on specific buftypes, defaults to |
Sweet! Btw for the optional fields there's an equivalent type called 'render.md.UserConfig'. I have a script to generate one from the other so they stay in sync. |
Ah! Good to know. I admit it was a subtle attempt to get it fixed or info on how to improve it on my side. 😄 |
Is your feature request related to a problem? Please describe.
Currently it looks like the signs added by this plugin use the background color of the

Normal
highlight group. This leads to effects like this:Describe the solution you'd like
Here are three possible solutions:
SignColumn
highlight group instead.The text was updated successfully, but these errors were encountered: