Add sp-forward-hybrid-sexp and sp-backward-hybrid-sexp #843
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.
This is like moving by lines except it jumps over the "logical lines", that is one statement spread over multiple lines. So in case we have something like
normal navigation by sexp would land after
$credentials
, then over the method chain and finally only at the(
it would jump to the end of the statement. The hybrid sexp recognizes this entire thing as one entity and jumps to the end of the logical line, which is at the semicolon.Note that this is NOT ALWAYS just "go to semicolon", it would work without semicolon just as fine. Also inside the
[...]
array the end of hybrid sexp is at the ending]
not at the end of the statement. In other words, it should recognize any statement spread over multiple line which is still one "node" in the AST.Super cool!