(Error Debugging): Remove stack-trace-on-error.

2 files changed, 4 insertions, 14 deletions

diff --git a/lispref/ChangeLog b/lispref/ChangeLog
index a0451009de0..105fbec9a7d 100644
--- a/lispref/ChangeLog
+++ b/lispref/ChangeLog
@@ -1,3 +1,7 @@
+2005-03-05  Richard M. Stallman  <rms@gnu.org>
+
+        * debugging.texi (Error Debugging): Remove stack-trace-on-error.
+
 2005-03-04  Lute Kamstra  <lute@gnu.org>
 
         * debugging.texi (Error Debugging): Document stack-trace-on-error.
diff --git a/lispref/debugging.texi b/lispref/debugging.texi
index 5886138eb55..07dfe18f283 100644
--- a/lispref/debugging.texi
+++ b/lispref/debugging.texi
@@ -166,20 +166,6 @@ this:
           (lambda () (setq debug-on-error t)))
 @end example
 
-When the debugger is entered, it shows a backtrace (@pxref{Using
-Debugger}).  If you like to see the backtrace when an error happens,
-but you do not want to enter the debugger, you can set the variable
-@code{stack-trace-on-error} to non-@code{nil}.
-
-@defopt stack-trace-on-error
-This variable determines whether a backtrace buffer is shown when an
-error is signalled and not handled.  If @code{stack-trace-on-error} is
-@code{t}, all kinds of errors display a backtrace; if it is
-@code{nil}, none do.  If the value is a list, an error only means to
-display a backtrace if one of its condition symbols appears in the
-list.
-@end defopt
-
 @node Infinite Loops
 @subsection Debugging Infinite Loops
 @cindex infinite loops