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.

Sign up for GitHub

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

Jump to bottom

Fix space key in edebug-eval-expression with lispy-mode on. #579

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

Fix space key in edebug-eval-expression with lispy-mode on. #579

wants to merge 2 commits into from

Conversation

daanturo
Copy link
Contributor

@daanturo daanturo commented Mar 15, 2021 •
edited
Loading

When typing in edebug-eval-expression with lispy-mode
on (lispy-mode was enabled for eval-expression), "SPC" key is always
forwarded to edebug-step-mode, making it hard to type " " without
quote-insert ("C-q").

Fix by checking lispy--edebug-commandp after knowing edebug-active is t.

Fixes #613 .

@dantlev01
Fix space in edebug-eval-expression.
cdb19c3 
When typing in `edebug-eval-expression` with `lispy-mode`
on (`lispy-mode` was enabled for eval-expression), "SPC" key is always
forwarded to `edebug-step-mode`, making it hard to type " " without
`quote-insert` ("C-q").
@coveralls
Copy link

coveralls commented Mar 15, 2021 •
edited
Loading

Coverage Status

Coverage decreased (-0.04%) to 62.73% when pulling fd5a9b3 on daanturo:space-in-M-;-while-edebug into 38a7df4 on abo-abo:master.

@daanturo daanturo mentioned this pull request Oct 30, 2021
Open
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Reviewers
No reviews
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

Successfully merging this pull request may close these issues.

Cannot type " " in eval-expression's prompt when using edebug
3 participants
@daanturo @coveralls @dantlev01