Fix: properly update highlights on colorscheme change #68
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Fixes incorrect highlight updates when colorscheme is changed. This is only relevant to this feature branch.
Prior to these changes, any "patched" devicon highlight was not "re-patched" when colorscheme is changed (by patched, I mean "create a separate highlight group for the devicon that inherits the winbar background highlights"). Now this is done.
Additionally, the
ColorScheme
autocmd event now schedules the updating of highlights instead of triggering it automatically. This is useful when the user sets some custom highlights after calling:colorscheme
. Prior to this, if the user did something like:the highlights would be created before the
WinBar
highlight is manually set, and thus not reflected in DropBar.Now, since the update is scheduled, the above example would be reflected in DropBar highlights.