From: William Harold Newman <wnewman@us...> - 2002-06-06 14:08:12
Update of /cvsroot/sbcl/sbcl/doc
In directory usw-pr-cvs1:/tmp/cvs-serv5315/doc
changed --noprogrammer behavior to support people building
interactive cores noninteractively...
...renamed --noprogrammer to --disable-debugger
...defined SB-EXT:DISABLE-DEBUGGER and SB-EXT:ENABLE-DEBUGGER
RCS file: /cvsroot/sbcl/sbcl/doc/sbcl.1,v
retrieving revision 1.16
retrieving revision 1.17
diff -u -d -r1.16 -r1.17
--- sbcl.1 1 Jun 2002 02:34:52 -0000 1.16
+++ sbcl.1 6 Jun 2002 14:08:09 -0000 1.17
@@ -270,8 +270,9 @@
Suppress the printing of any banner or other informational message at
-startup. (This makes it easier to write Lisp programs which work in
-Unix pipelines. See also the "--noprogrammer" and "--noprint" options.)
+startup. (This makes it easier to write Lisp programs which work
+cleanly in Unix pipelines. See also the "--noprint" and
In the future, runtime options may be added to control behavior such
@@ -310,9 +311,11 @@
When ordinarily the toplevel "read-eval-print loop" would be executed,
execute a "read-eval loop" instead, i.e. don't print a prompt and
don't echo results. Combined with the --noinform runtime option, this
-makes it easier to write Lisp "scripts" which work in Unix pipelines.
+makes it easier to write Lisp "scripts" which work cleanly in Unix
+This is equivalent to --eval '(sb-ext:disable-debugger)'.
By default, a Common Lisp system tries to ask the programmer for help
when it gets in trouble (by printing a debug prompt on *DEBUG-IO*).
However, this is not useful behavior for a system running with no
@@ -323,6 +326,8 @@
*DEBUGGER-HOOK* to output a backtrace, then exit the process with a
failure code. Because it is implemented by modifying special variables,
its effects persist in .core files created by SB-EXT:SAVE-LISP-AND-DIE.
+(If you want to undo its effects, see the SB-EXT:ENABLE-DEBUGGER
Regardless of the order in which --sysinit, --userinit, and --eval