procyberian/emacs
1
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity Actions

(Using Debugger): Mention @code{eval-expression-debug-on-error}

Browse source 
Fixes: debbugs:8549
This commit is contained in:
Lars Magne Ingebrigtsen 2011-07-15 15:16:11 +02:00
parent 1d698799d3
commit 662498421e
2 changed files with 15 additions and 0 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

5
doc/lispref/ChangeLog
View file

@ -1,3 +1,8 @@
2011-07-15 Lars Magne Ingebrigtsen <larsi@gnus.org>
* debugging.texi (Using Debugger): Mention
@code{eval-expression-debug-on-error} (bug#8549).
2011-07-14 Eli Zaretskii <eliz@gnu.org>
* display.texi (Other Display Specs): Document that `left-fringe'

10
doc/lispref/debugging.texi
View file

@ -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