Fix SpecialKey linking issue for :dig visibility - #115
Open
waterkip wants to merge 1 commit into
Open
Conversation
When using diacritics the colorscheme makes it hard to read the digraph symbols this is due to the `hi! link SpecialKey Whitespace' setting that is implemented when not in nvim. I don't know the reason for this being in so I added a configuration item to tweak this behavior. It is fully backwards compatible. Closes: cocopon#114 Signed-off-by: Wesley Schwengle <wesleys@opperschaap.net>
waterkip
force-pushed
the
whitespace
branch
2 times, most recently
from
August 26, 2025 01:28
bbd69b8 to
f8c6a2b
Compare
This file contains hidden or 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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
When using diacritics the colorscheme makes it hard to read the digraph symbols this is due to the `hi! link SpecialKey Whitespace' setting that is implemented when not in nvim. I don't know the reason for this being in so I added a configuration item to tweak this behavior. It is fully backwards compatible.
Closes: #114