summaryrefslogtreecommitdiff
path: root/lispref/debugging.texi
diff options
context:
space:
mode:
authorRichard M. Stallman <rms@gnu.org>2005-03-05 13:06:14 +0000
committerRichard M. Stallman <rms@gnu.org>2005-03-05 13:06:14 +0000
commitd21783879a16cdf208f28a67fe6d275a317c3a68 (patch)
tree86ab50979e6e6f39161bb91b049f8b55663d9c51 /lispref/debugging.texi
parent70dce461eb36df01014ba2e2bf8ee3361fd70809 (diff)
(Error Debugging): Remove stack-trace-on-error.
Diffstat (limited to 'lispref/debugging.texi')
-rw-r--r--lispref/debugging.texi14
1 files changed, 0 insertions, 14 deletions
diff --git a/lispref/debugging.texi b/lispref/debugging.texi
index 5886138eb5..07dfe18f28 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