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

:read-string is not interrupted on slime-restart-inferior-lisp #720

Open
Affonso-Gui opened this issue Apr 29, 2022 · 0 comments
Open

:read-string is not interrupted on slime-restart-inferior-lisp #720

Affonso-Gui opened this issue Apr 29, 2022 · 0 comments

Comments

@Affonso-Gui
Copy link

How to recreate:

(read)
M-x slime-restart-inferior-lisp
10

What is expected:
The read is aborted and the new evaluation request is processed.

What happens:
The new evaluation request serves as output to the read call and is not evaluated.

*slime-events* abbreviated log:

(:emacs-rex
 (swank-repl:listener-eval "(read)\n")
 "COMMON-LISP-USER" :repl-thread 7)
(:read-string 1 1)
(:emacs-rex
 (swank:quit-lisp)
 "COMMON-LISP-USER" :repl-thread 8)
(:emacs-rex
 (swank:connection-info)
 "COMMON-LISP-USER" t 1)

;; ...

(:emacs-return-string 1 1 "10\n")

The simplest way to solve this would be to add a :read-aborted call, although I am not sure if we should also include a debugger window to prompt the user (similarly to when C-c C-c ing a read).

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

No branches or pull requests

1 participant