0.7.7.20-backend-cleanup-1.4:

[sbcl.git] / doc / sbcl.1

diff --git a/doc/sbcl.1 b/doc/sbcl.1
index 0fcc298..908f9a1 100644 (file)
--- a/doc/sbcl.1
+++ b/doc/sbcl.1
@@ -61,7 +61,10 @@ Many people like to run SBCL, like other Lisp systems, as a subprocess
 under Emacs. The Emacs "ilisp" mode provides many convenient features,
 like command line editing, tab completion, and various kinds of
 coupling between Common Lisp source files and the interactive SBCL
-subprocess.
+subprocess, but can be somewhat fragile because it tries to be so
+clever and intimate in its interactions with the Lisp subprocess. In
+case of ilisp problems, running SBCL in the Emacs "shell" mode can a
+useful substitute.
 
 .SH OVERVIEW
 
@@ -169,7 +172,7 @@ SAVE-LISP does.
 
 (Why doesn't SBCL support more extensions? Why drop all those nice
 extensions from CMU CL when the code already exists? This is a
-frequently asked question on the mailing list. In other cases, it's a
+frequently asked question on the mailing list. In some cases, it's a
 design philosophy issue: arguably SBCL has done its job by supplying a
 stable FFI, and the right design decision is to move functionality
 derived from that, like socket support, into separate libraries,