Skip char and string literals when highlighting comments#463
Merged
SuperAuguste merged 1 commit intozigtools:masterfrom Mar 2, 2022
Merged
Skip char and string literals when highlighting comments#463SuperAuguste merged 1 commit intozigtools:masterfrom
SuperAuguste merged 1 commit intozigtools:masterfrom
Conversation
Contributor
|
nice |
Contributor
|
can you post a screenshot of what it looks like with these changes |
Contributor
Author
|
Yep! Here is what it looks like: |
Member
|
Thanks! |
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
4 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.
The comment highlighting appears to take priority over string and char literals, leading to syntax highlighting like this:
These changes should make it skip string and char literals when scanning for comments.