This repository has been archived by the owner on Apr 29, 2024. It is now read-only.
More tree-sitter navigation / selection modes #313
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
hadronized
force-pushed
the
tree-sitter-nav
branch
3 times, most recently
from
f4eb083
to
1bad60f
Compare
hadronized
force-pushed
the
tree-sitter-nav
branch
from
1bad60f
to
5f0a713
Compare
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
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.
I want to use that PR to also refactor a bit the usage of tree-sitter. For instance, we use
QueryCaptureeverywhere, while we actually want to useNode, so that we can reuse those functions for doing things like expanding / collapsing selections; moving to the next sibling, parent, etc.