diff options
| -rw-r--r-- | lispref/ChangeLog | 4 | ||||
| -rw-r--r-- | lispref/debugging.texi | 14 |
2 files changed, 4 insertions, 14 deletions
diff --git a/lispref/ChangeLog b/lispref/ChangeLog index a0451009de..105fbec9a7 100644 --- a/lispref/ChangeLog +++ b/lispref/ChangeLog @@ -1,3 +1,7 @@ +2005-03-05 Richard M. Stallman <[email protected]> + + * debugging.texi (Error Debugging): Remove stack-trace-on-error. + 2005-03-04 Lute Kamstra <[email protected]> * debugging.texi (Error Debugging): Document stack-trace-on-error. 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 |