-
-
Notifications
You must be signed in to change notification settings - Fork 108
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
consider using blend
opt of vim.api.nvim_set_hl()
instead of alpha_blend()
#251
Comments
@tmillr I intentionally used Even though the |
I apologize if my original post is confusing. When I posted this I didn't understand |
No worries! @tmillr Since some Neovim plugins use the BTW, Thank you for reporting, contributing, and sponsoring this project. Your efforts are appreciated! I'm closing this issue as complete, and it can be reopened in the future for further discussion. |
Why?
It's builtin to Neovim.
It may handle blending with different background colors dynamically (although this needs further investigation). For example, it seems that the current use of
alpha_blend()
always assumes the bg to be the global/default bg for the current theme for any given hl group and position on the screen? But that is not necessarily always the case (a hl group may havebg
set and set to a different color, there may be extmarks setting the bg color arbitrarily at runtime, the highlight could be appearing in a floating window which has a different bg than the default/global, etc. My point is that it might be that Neovim'sblend
option forvim.api.nvim_set_hl()
handles all of these cases of blending with arbitrary bg colors dynamically at runtime - although I am not totally sure of this and it needs further investigation; it could be that it only considers the bg setting for just that one, single hl group specified toset_hl()
).The text was updated successfully, but these errors were encountered: