0.7.7.20-backend-cleanup-1.1:

[sbcl.git] / doc / sbcl.1

diff --git a/doc/sbcl.1 b/doc/sbcl.1
index ffe4b37..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,
@@ -352,12 +355,15 @@ chance to see it.
 
 .SH SYSTEM REQUIREMENTS
 
-Unlike its distinguished ancestor CMU CL, SBCL currently runs only on
-X86 (Linux, FreeBSD, and OpenBSD), Alpha (Linux), and SPARC (Linux).
+SBCL currently runs on
+X86 (Linux, FreeBSD, and OpenBSD), Alpha (Linux, Tru64), PPC
+(Linux) and SPARC (Linux and Solaris 2.x).
 For information on other ongoing and possible ports, see the
 sbcl-devel mailing list, and/or the web site.
 
-SBCL requires on the order of 16Mb RAM to run on X86 systems. 
+SBCL requires on the order of 16Mb RAM to run on X86 systems, 
+though for all but the smallest programs would be happier with 32Mb
+or more.
 
 .SH ENVIRONMENT
 
@@ -485,8 +491,13 @@ handled specially by certain type expanders.)
 
 .SH REPORTING BUGS
 
-To report a bug, please send mail to sbcl-help@lists.sourceforge.net
-or sbcl-devel@lists.sourceforge.net.
+To report a bug, please send mail to the mailing lists sbcl-help or
+sbcl-devel. You can find the complete mailing list addresses on the
+web pages, <http://sbcl.sourceforge.net/>. (You may also find fancy
+SourceForge bug-tracking machinery there, but don't be fooled. As of
+2002-07-25 anyway, we don't actively monitor that machinery, and it
+exists only because we haven't been able to figure out how to turn
+it off.)
 
 As with any software bug report, it's most helpful if you can provide
 enough information to reproduce the symptoms reliably, and if you say