You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
CL-USER> (testpkg:testfunc "teststring")
; Debugger entered on #<SB-INT:SIMPLE-READER-PACKAGE-ERROR "The symbol ~S is not external in the ~A package." {236425E1}>
[1] CL-USER>
; Evaluation aborted on #<SB-INT:SIMPLE-READER-PACKAGE-ERROR "The symbol ~S is not external in the ~A package." {236425E1}>
; Server side close
; --------------------------------------------------------
whenever I happen to have a coding error. The repl still runs in the backgrund. I then kill the buffer and start sly again. I am then asked:
[sly] Switch to open connection?
(Customize ``sly-command-switch-to-existing-lisp' to avoid this prompt.)
Connections:
sbcl
(start a new one)
When I connect ot the existing one, everything seems fine.
Can this behavior be prevented?
I run Emacs 28.2. on Windows 10.
regards
Marc
The text was updated successfully, but these errors were encountered:
Hi,
I experience the following kind of error
whenever I happen to have a coding error. The repl still runs in the backgrund. I then kill the buffer and start sly again. I am then asked:
When I connect ot the existing one, everything seems fine.
Can this behavior be prevented?
I run Emacs 28.2. on Windows 10.
regards
Marc
The text was updated successfully, but these errors were encountered: