fix: Match C source highlighting to VSCode #227
Merged
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
|
Looking at these screenshots, it seems like the background in Neovim needs to become darker. Also, what you see is the |
olimorris
reviewed
Jan 26, 2024
I think it's how they're rendered in the terminal and VS code itself; VSCode background verses Neovim background. |
The theme was missing quite a few things to make it match VSCode.
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.
The theme was missing quite a few things to make it match VSCode.
VSCode:
Neovim:
I can't do anything about the
LOGline just yet. The tree-sitter grammar isn't detailed enough and clangd doesn't seems to provide good tokens here.