From 662498421ef4b06cfa6e27d6be2b09e80ec2bff9 Mon Sep 17 00:00:00 2001 From: Lars Magne Ingebrigtsen Date: Fri, 15 Jul 2011 15:16:11 +0200 Subject: [PATCH] (Using Debugger): Mention @code{eval-expression-debug-on-error} Fixes: debbugs:8549 --- doc/lispref/ChangeLog | 5 +++++ doc/lispref/debugging.texi | 10 ++++++++++ 2 files changed, 15 insertions(+) diff --git a/doc/lispref/ChangeLog b/doc/lispref/ChangeLog index 153d7e839c3..cf6e3482efb 100644 --- a/doc/lispref/ChangeLog +++ b/doc/lispref/ChangeLog @@ -1,3 +1,8 @@ +2011-07-15 Lars Magne Ingebrigtsen + + * debugging.texi (Using Debugger): Mention + @code{eval-expression-debug-on-error} (bug#8549). + 2011-07-14 Eli Zaretskii * display.texi (Other Display Specs): Document that `left-fringe' diff --git a/doc/lispref/debugging.texi b/doc/lispref/debugging.texi index ed146453df7..d9e807afb88 100644 --- a/doc/lispref/debugging.texi +++ b/doc/lispref/debugging.texi @@ -306,6 +306,16 @@ and it is wise to go back to the backtrace buffer and exit the debugger the debugger gets out of the recursive edit and kills the backtrace buffer. + When the debugger has been entered, the @code{debug-on-error} +variable is temporarily set according to +@code{eval-expression-debug-on-error}. If the latter variable is +non-@code{nil}, @code{debug-on-error} will temporarily be set to +@code{t}. This means that any further errors that occur while doing a +debugging session will (by default) trigger another backtrace. If +this is not want you want, you can either set +@code{eval-expression-debug-on-error} to @code{nil}, or set +@code{debug-on-error} to @code{nil} in @code{debugger-mode-hook}. + @cindex current stack frame The backtrace buffer shows you the functions that are executing and their argument values. It also allows you to specify a stack frame by -- 2.39.2