Hi,
As I checked with the top-level repl, si::*break-level* is already 1.
If I eval (let ((si::*break-level* 1)) (si::tpl)) in the slime buffer,
it won't abort connection anymore. But I lose the capability of using
SLIME's debugging buffer. The errors will be directly dumped to the
top-level.
Anot
Are you running ECL from the sh/bash shell in Emacs? I've run into
problems with that in ECL, it seems to point to some bug in slime but I
haven't had a chance to investigate. It could equally be something I'm
doing wrong. But try the following:
- Double check your .eclrc resource file a
Thanks for the reply. But I don't quite understand what it means. I
was doing something similar to
https://chriskohlhepp.wordpress.com/embedding-lisp-in-cplusplus-a-recipe/
. When I hit C-c in the console, I drop into the top-level REPL. I
typed:
> (swank:create-server :port 4005)
;; Swank started
Hello,
if you call lisp forms from C code (after cl_boot), then you have no set
handler, so if your code signals a condition, then it goes uncought. If
that's a case, you could do something, what toplevel does (setting
handlers etc), or set si::*break-level* to 1 and call tpl:
(let ((si::*break-l
bruce li writes:
> Hi, there,
> I'm pretty new to ECL. I'm currently considering embedding ECL in a
> game engine. When I interactively interrupt the program and drop into
> the repl, I load up swank with quicklisp and create swank server with
> (swank:create-server :port 4005). I can connect to
Hi, there,
I'm pretty new to ECL. I'm currently considering embedding ECL in a
game engine. When I interactively interrupt the program and drop into
the repl, I load up swank with quicklisp and create swank server with
(swank:create-server :port 4005). I can connect to it from SLIME. But
any error
