lsp semantic highlight support #8
Open
Conversation
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
Author
|
This PR will resolve #2 |
|
@phha Any opinion on merging this? My Please at least consider this 🙏 |
|
For what it's worth, I have forked this repo, applied this patch, and everything works as intended. Thanks @hexbloom! |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
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.
Hey there! Thanks for the great theme. I recently upgraded to NeoVim 0.10.0 which has support for semantic highlighting. I noticed that this theme didn't had support for it, so I threw together this commit, see the below image for the result. It's based off of the treesitter highlights but I commented most of them out to be more minimal with the implementation.
Let me know if this looks good or if some of the options should be tweaked!