Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Code cleanup after #649: removed unnecessary bounds + string, and removed clojure-dot rule #650

Open
wants to merge 3 commits into
base: master
Choose a base branch
from

Conversation

RuijieYu
Copy link
Contributor

@RuijieYu RuijieYu commented Apr 5, 2023

Blocked by #649.

The first two commits are #649 itself, and the only commit of interest is 949e6d1.

The PR's goal is to remove clojure-dot rule entirely. This is because the clojure-dot rule is always covered by unsafe symbol, which can be tested by letting lispy parse (. hello world).

@RuijieYu RuijieYu changed the title Cleanup bug 648 clisp dot in symbol Code cleanup after #649: removed unnecessary bounds + string, and removed clojure-dot rule Apr 5, 2023
Fixes bug#653.

* lispy-test.el
(lispy-simulate-key) (lispy-simulate-keys) (lispy-simulate-expect):
Added facilities to assert results after a given set of keypresses.
(lispy-read-unsafe-chars): added regression tests for bug#648.
Fixes bug#648.

* lispy.el lispy--symbol-safe-chars: define list of safe chars.
(lispy--read): protect against unsafe chars in a symbol.
(lispy--replace-regexp-in-code): add predicate to only replace on match data.
lispy.el (lispy--read) (lispy--insert): removed unreachable clojure dot rule,
because it is always covered by the unsafe character rule.
@RuijieYu RuijieYu force-pushed the cleanup-bug-648-clisp-dot-in-symbol branch from 6ce8d1a to 949e6d1 Compare April 7, 2023 09:30
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant