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

Breaks some other highlight plugins #8

Open
erikw opened this issue Sep 13, 2022 · 2 comments
Open

Breaks some other highlight plugins #8

erikw opened this issue Sep 13, 2022 · 2 comments

Comments

@erikw
Copy link

erikw commented Sep 13, 2022

First, thanks for this great plugin. I very much enjoy not having to manually toggle all vim instances when the system mode changes!

Lately I've came across at least three plugins that does something with text highlighting that does not work super great with dark-notify.

Would it be possible to make this plugin more compatible by default with other plugins? Or would you have an idea on how to work around using any of the two latter plugins above together with dark-notify?

I'm on Neovim v0.7.2.

Thanks in advance!

@cormacrelf
Copy link
Owner

Making dark-notify "more compatible by default" is not really possible. Literally all it's doing is changing the colorscheme. If plugins cannot handle a change in colorscheme, that's their fault. Unfortunately this is simply very common, so I built the onchange feature. You will have to figure out for yourself how to "refresh" various plugins, but I would consider it a bug in many plugins if they don't do it automatically. If you file bugs on them, you do not have to mention dark-notify. Just say "how do I make your plugin respond to colorscheme changes like it should".

For nvim-cursorline, I read the source code, and it seems to set the highlight in a VimEnter autocommand. Why would it do that? I think that's just a dumb approximation for "do this once": a perfect manifestation of vim plugin authors' collective delusion that nobody ever changes the colorscheme outside their vimrc. Maybe try changing this autocommand to au ColorScheme *. I think that's a thing.

@cormacrelf
Copy link
Owner

One more thing, I am not sure if many people are aware of this but colorscheme changes always clear all highlight groups. It's a bulldozer.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants