fix: the paredit-splice should not backward 1 form if current point already at open-char #1709
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 pr fixes the
matched level
ofopen-char
andclosed-char
.To fix cases like: #1612
Before this pr: the
paredit-splice
treatstring between open-char and closed-char
andclosed-char
as thesame form
, but treat theopen-char
as the(form-offset (current-point) -1)
.After this pr: the
paredit-splice
treatopen-char
,string between open-char and closed-char
andclosed-char
as thesame form
.For this test-case:
Before this pr:
After this pr: