0.7.10.32:

[sbcl.git] / doc / sbcl.1

diff --git a/doc/sbcl.1 b/doc/sbcl.1
index 0fcc298..5ccfe15 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,
@@ -264,9 +267,11 @@ Supported runtime options are
 .TP 3
 .B --core <corefilename>
 Run the specified Lisp core file instead of the default. (See the FILES
-section.) Note that if the Lisp core file is a user-created core file, it may
-run a nonstandard toplevel which does not recognize the standard toplevel
-options.
+section for the standard core, or the system documentation for
+SB-INT:SAVE-LISP-AND-DIE for information about how to create a 
+custom core.) Note that if the Lisp core file is a user-created core
+file, it may run a nonstandard toplevel which does not recognize the
+standard toplevel options.
 .TP 3
 .B --noinform
 Suppress the printing of any banner or other informational message at
@@ -282,7 +287,7 @@ Runtime options, including any --end-runtime-options option,
 are stripped out of the command line before the
 Lisp toplevel logic gets a chance to see it.
 
-Supported toplevel options for the standard SBCL core are
+The toplevel options supported by the standard SBCL core are
 .TP 3
 .B --sysinit <filename>
 Load filename instead of the default system-wide initialization file.
@@ -517,8 +522,8 @@ executable program containing some low-level runtime support and
 a loader, used to read sbcl.core
 .TP
 .I sbcl.core
-dumped memory image containing most of SBCL, to be loaded by the
-'sbcl' executable
+dumped memory image containing most of SBCL, to be loaded by
+the 'sbcl' executable
 .TP
 .I sbclrc
 optional system-wide startup script (in an etc-ish system