[slime-devel] reporting SLIME errors from Lisp

Helmut Eller heller at common-lisp.net
Fri Jul 28 15:33:30 UTC 2006

* Taylor R Campbell [2006-07-24 19:53+0200] writes:

> What's the best way to report errors in SLIME that were detected on
> the Lisp side, such as `no package FOO'?  Right now in SLIME48 I just
> abort the RPC and log a message to the console about the error, but
> this is suboptimal, because all the user sees is `Evaluation aborted'
> or `Synchronous Lisp Evaluation aborted.'  Perhaps :ABORT responses to
> RPCs could include optional error messages?

If the error is worth to fix just drop into the debugger.  Otherwise
catch the error, return a tagged result like `(ok <normal-value>)' or
`(error <reason>)', and do whatever is appropriate on the Emacs side.

If you just want to print something you could also send a
:background-message packet.


More information about the slime-devel mailing list