[Fix #443] Don't consider #? as starting non-logical sexp #444
Conversation
This file contains hidden or 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
Malabarba
approved these changes
Aug 7, 2017
|
Travis test broke for unrelated reason. |
|
Merged! Thanks a ton. |
|
I was just going to say this needs to have a regression unit test. :-) |
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.
Fixing this in a simplest way I can think of. Judging from the docs of
clojure--looking-at-non-logical-sexp#?should not even be considered as non-logical sexps under any circumstances.I think
?in that regexp is some kind of legacy remnant.#?@are now marked as prefix chars andbackward-sexpdoes the right thing on prefixed sexps.