Re: Couple of Emacs hacks

Luke Gorrie <luke@xxxxxxxxxxxx> writes:

> Slime has too few features to be a whizzy-bang development environment
> just yet. But it's easy to setup (provided you have a recent CMUCL
> snapshot), and should work fine with GNU Emacs 21 or XEmacs
> 21. Comments and suggestions welcome!

Any plans to reuse Distel for Slime?  Currently Emacs blocks in
slime-compile-file.  A whizzy-bang development environment should
definitely not do that.

I like that Slime uses a protocol for the communication between Emacs
and CMUCL.  That seems to be cleaner than ILISP's prompt guessing.
But currently it is a bit confusing that some of output gets displayed
in the echo area, but most output goes (silently) to the
*inferior-lisp* buffer.  Do you plan to implement something like
Hemlock's typescript streams?  Then you could redirect the output that
goes to *compiler-error-output* to the echo area.

It would be nice if there where some way to interact with the
debugger.  Currently the compilation is aborted on every error.
Perhaps you could install a debugger hook that displays the
*inferior-lisp* window before entering the debugger.

There is still a some way to go until Slime is a serious ILISP
alternative, but it's worthwhile goal.  Is there a way and I could
help you?

--helmut