0.9.3.14: debugger streams

[sbcl.git] / doc / sbcl.1

diff --git a/doc/sbcl.1 b/doc/sbcl.1
index 4abdbdd..16f28bf 100644 (file)
--- a/doc/sbcl.1
+++ b/doc/sbcl.1
@@ -58,10 +58,12 @@ give you another prompt, and wait for your next input. E.g.
   *
 
 Many people like to run SBCL, like other Lisp systems, as a subprocess
-under Emacs. The Emacs "ilisp" and "Slime" modes provide many
+under Emacs. The Emacs "Slime" and "ilisp" modes provide many
 convenient features, like command line editing, tab completion, and
 various kinds of coupling between Common Lisp source files and the
-interactive SBCL subprocess.
+interactive SBCL subprocess, but they can be somewhat fragile wrt.
+packages and readtables, in which case SBCL in the Emacs "shell" mode
+can a useful substitute.
 
 .SH OVERVIEW
 
@@ -319,14 +321,12 @@ in trouble (by printing a debug prompt, then listening, on
 with no programmer available, and this option tries to set up more
 appropriate behavior for that situation. This is implemented by
 redefining INVOKE-DEBUGGER so that any call exits the process with a
-failure code after printing a backtrace, and by redefining *DEBUG-IO*
-to send its output to *ERROR-OUTPUT* and to raise an error if any
-input is requested from it. (Note that because it is implemented by
-modifying special variables and FDEFINITIONs, its effects persist in
-.core files created by SB-EXT:SAVE-LISP-AND-DIE. If you want to undo
-its effects, e.g. if you build a system unattended and then want to
-operate a derived system interactively, see the SB-EXT:ENABLE-DEBUGGER
-command.)
+failure code after printing a backtrace. (Note that because it is
+implemented by modifying special variables and FDEFINITIONs, its
+effects persist in .core files created by SB-EXT:SAVE-LISP-AND-DIE. If
+you want to undo its effects, e.g. if you build a system unattended
+and then want to operate a derived system interactively, see the
+SB-EXT:ENABLE-DEBUGGER command.)
 .PP
 
 Regardless of the order in which --sysinit, --userinit, and --eval