fix: preserve PrecognitionHighlight through colorscheme changes #90
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
TymekDev
force-pushed
the
fix/preserve-highlights
branch
from
45e9243
to
c5a40a9
Compare
|
@tris203 tests passed locally for me. However, as I developed them, I initially had this block at the top of |
|
Thanks! |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
I have taken a look what autocmds I have for ColorScheme. Turns out quite a few plugins have callbacks to re-setup their highlights. I loosely based this solution on oil.nvim and gitsigns.nvim.
@tris203 FYI I haven't run or taken a look at the tests yet.
Closes #89