From: Aaron Solochek
Subject: slime and clisp: any way to get stack trace info?
Date:
Message-ID: <4592F2C5.2080907@aberrant.org>
I would really like to use slime for my clisp mode, but it has a couple
of big problems, one of which I haven't been able to work around yet.
The first problem (that I hacked around) was that the output from
ext:run-program wasn't showing up in the slime-repl buffer, only the
inferior-lisp buffer. I wrote a function that which grabs stuff from
the inferior-lisp buffer and sticks it in slime-repl, and while that
works, it strikes me as a very ugly solution.
The real problem I'm having now though is that when I hit a compilation
error, the sldb stuff doesn't contain any useful information.
For instance, this is what I get with an error in slime:
> #
>
> in toplevel-form:
> #1=# #2=
>
> in toplevel-form:
> (collection . #3=#) #2#
>
> in toplevel-form:
> (conditional-compile-toplevel include-behaviors . #3#) #2#
And this is what I get for the same error in standard emacs lisp mode:
> expand: unknown function 'test-foo?' in form:
> (test-foo?)
>
> in form:
> (test-foo?)
>
> in file:
> C:\home\cvs-tree\toys\systems\test.tl
> (Toplevel form ends near line 248.)
Obviously the second is much more useful output. Is there any way to
get that output from slime?
-Aaron