Steven E. Harris wrote:
Sorry, I wasn't clear. What I meant regarding CLISP is that if I start up its REPL from a shell, just running CLISP bare outside of SLIME, *standard-output* does appear in the CLISP REPL. When I run SLIME over CLISP, *standard-output* does /not/ get echoed to SLIME's REPL. The only way to see *standard-output* is to visit the *inferior-lisp* buffer.
I see the behavior that you describe in my configuration, too.
I added the following line to ~/.swank.lisp to restore the earlier behavior:
(setq `SWANK:*GLOBALLY-REDIRECT-IO*' t)
Here is the description from the Slime manual:
`SWANK:*GLOBALLY-REDIRECT-IO*' When true this causes the standard streams (`*standard-output*', etc) to be globally redirected to the REPL in Emacs. When `NIL' (the default) these streams are only temporarily redirected to Emacs using dynamic bindings while handling requests. Note that `*standard-input*' is currently never globally redirected into Emacs, because it can interact badly with the Lisp's native REPL by having it try to read from the Emacs one.
You can read the entry in Emacs if you have slime.info properly configured by entering the following in the minibuffer:
M-x: (info "(slime) Other configurables")