feat: support blink.cmp #372
Open
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
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.
add support for Saghen/blink.cmp, related issue #366
The majority come from default cmp highlight mapping from blink.cmp and existing cmp kind highlight group,
BlinkCmpSourceis my own speculations.Screenshot:
Dark Hard
Light Hard
Update: Use
GruvboxBg4asBlinkCmpGhostTexthighlight group.Personally I think the default
NonText( link toGruvboxBg0) is hard to read when it comes forBlinkCmpGhostText.Screenshot from Light Hard
Screenshot from Dark Hard
Change to
GruvboxBg4will be much easier to read IMO.Screenshot from Light Hard
Screenshot from Dark Hard
