emacs-diffs
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[Emacs-diffs] /srv/bzr/emacs/trunk r105226: (Using Debugger): Mention @c


From: Lars Magne Ingebrigtsen
Subject: [Emacs-diffs] /srv/bzr/emacs/trunk r105226: (Using Debugger): Mention @code{eval-expression-debug-on-error}
Date: Fri, 15 Jul 2011 15:16:11 +0200
User-agent: Bazaar (2.3.1)

------------------------------------------------------------
revno: 105226
fixes bug(s): http://debbugs.gnu.org/8549
committer: Lars Magne Ingebrigtsen <address@hidden>
branch nick: trunk
timestamp: Fri 2011-07-15 15:16:11 +0200
message:
  (Using Debugger): Mention @code{eval-expression-debug-on-error}
modified:
  doc/lispref/ChangeLog
  doc/lispref/debugging.texi
=== modified file 'doc/lispref/ChangeLog'
--- a/doc/lispref/ChangeLog     2011-07-14 17:28:42 +0000
+++ b/doc/lispref/ChangeLog     2011-07-15 13:16:11 +0000
@@ -1,3 +1,8 @@
+2011-07-15  Lars Magne Ingebrigtsen  <address@hidden>
+
+       * debugging.texi (Using Debugger): Mention
+       @code{eval-expression-debug-on-error} (bug#8549).
+
 2011-07-14  Eli Zaretskii  <address@hidden>
 
        * display.texi (Other Display Specs): Document that `left-fringe'

=== modified file 'doc/lispref/debugging.texi'
--- a/doc/lispref/debugging.texi        2011-01-25 04:08:28 +0000
+++ b/doc/lispref/debugging.texi        2011-07-15 13:16:11 +0000
@@ -306,6 +306,16 @@
 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
address@hidden  If the latter variable is
address@hidden, @code{debug-on-error} will temporarily be set to
address@hidden  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
address@hidden to @code{nil}, or set
address@hidden 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


reply via email to

[Prev in Thread] Current Thread [Next in Thread]