*STANDARD-OUTPUT* of functions called from the REPL is going to *inferior-lisp* not to the REPL as it used to. I noticed this when calling DISASSEMBLE; the disassembly appears in the *inferior-lisp* buffer.
I'm using SBCL 1.0.29 on Windows with SLIME 2009-06-29. This behaviour was introduced well before today, though I haven't done the usual CVS binary search to find out when.
I'm open to the idea that this is not a general problem and that something in my setup is screwing with SLIME, but what could it be?
Thanks in advance as usual,
Graham
graham@gorgeous.org writes:
*STANDARD-OUTPUT* of functions called from the REPL is going to *inferior-lisp* not to the REPL as it used to. I noticed this when calling DISASSEMBLE; the disassembly appears in the *inferior-lisp* buffer.
I'm using SBCL 1.0.29 on Windows with SLIME 2009-06-29. This behaviour was introduced well before today, though I haven't done the usual CVS binary search to find out when.
I'm open to the idea that this is not a general problem and that something in my setup is screwing with SLIME, but what could it be?
Thanks in advance as usual,
This is a known bug, but unfortunately it's still not fixed. As a quick workaround you can evaluate (setf *standard-output* (swank::connection.user-output swank::*emacs-connection*)) at the REPL.
Stas Boukarev stassats@gmail.com writes:
graham@gorgeous.org writes:
*STANDARD-OUTPUT* of functions called from the REPL is going to *inferior-lisp* not to the REPL as it used to. I noticed this when calling DISASSEMBLE; the disassembly appears in the *inferior-lisp* buffer.
This is a known bug, but unfortunately it's still not fixed. As a quick workaround you can evaluate (setf *standard-output* (swank::connection.user-output swank::*emacs-connection*)) at the REPL.
Thanks, that did the trick.
Graham
Stas Boukarev stassats@gmail.com writes:
This is a known bug, but unfortunately it's still not fixed.
Here's another thread on this same problem:
http://thread.gmane.org/gmane.lisp.slime.devel/8442
On Thu, 02 Jul 2009 19:51:52 -0400 "Steven E. Harris" seh@panix.com wrote:
Here's another thread on this same problem:
Thanks, that thread was most useful to me today.
"Steven E. Harris" seh@panix.com writes:
Here's another thread on this same problem:
I updated my SLIME installation today and found that content written to *standard-output* goes to the SLIME REPL once again. That's great.
Did something change to make this so? I didn't catch it in the occasional change log messages.
"Steven E. Harris" seh@panix.com writes:
"Steven E. Harris" seh@panix.com writes:
Here's another thread on this same problem:
I updated my SLIME installation today and found that content written to *standard-output* goes to the SLIME REPL once again. That's great.
Did something change to make this so? I didn't catch it in the occasional change log messages.
http://article.gmane.org/gmane.lisp.slime.devel/8750