Scanner skip changes #95
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
For several tokens, `advance(skip=true)` could be called after `mark_end`. This sets the start of the token past the end, so it was returned as zero-width. Apparently syntax highlighting doesn't work well with zero-width tokens.
keidax
force-pushed
the
keidax/scanner-skip-changes
branch
from
cbafa41 to
57476f0
Compare
nobodywasishere
approved these changes
Jan 9, 2025
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.
For several tokens,
advance(skip=true)could be called aftermark_end. This sets the start of the token past the end, so it was returned as zero-width. Apparently syntax highlighting doesn't work well with zero-width tokens.I'm also adding the first set of highlighting tests, using the neovim queries for now.