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.
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Add syntax table property for comment semantic tokens. #3696
base: master
Are you sure you want to change the base?
Add syntax table property for comment semantic tokens. #3696
Changes from 1 commit
2a9bb3b
918de69
ad36e4f
c999198
4b68c57
File filter
Filter by extension
Conversations
Jump to
There are no files selected for viewing
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
with the way this is used, I think it'd make sense to always return non-nil
beg
andend
, withbeg
orend
remaining unmodified if they don't happen to overlap with comment tokens. Maybe the function could also be renamed to something likeextend-region-to-include-comment-tokens
or something like that (plus the prefix, of course), in my opinion that would be slightly more intuitiveThere was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
given that
lsp--semantic-tokens-fontify
removes comment syntax right at the outset, this call tolsp-semantic-tokens--remove-comment-syntax-strict
might needlessly degrade performance? Or is this call necessary for some reason I don't see right now?