[Emacs-diffs] /srv/bzr/emacs/emacs-24 r110839: Document debugger-bury-or-kill

[Glenn Morris]

------------------------------------------------------------
revno: 110839
committer: Glenn Morris <address@hidden>
branch nick: emacs-24
timestamp: Sat 2012-11-10 17:16:25 -0800
message:
  Document debugger-bury-or-kill
  
  * doc/lispref/debugging.texi (Using Debugger): Mention debugger-bury-or-kill.
  
  * lisp/emacs-lisp/debug.el (debugger-bury-or-kill): Doc tweak.
  
  * etc/NEWS: Related edit.
modified:
  doc/lispref/ChangeLog
  doc/lispref/debugging.texi
  etc/NEWS
  lisp/ChangeLog
  lisp/emacs-lisp/debug.el

=== modified file 'doc/lispref/ChangeLog'
--- a/doc/lispref/ChangeLog     2012-11-11 00:58:51 +0000
+++ b/doc/lispref/ChangeLog     2012-11-11 01:16:25 +0000
@@ -1,6 +1,7 @@
 2012-11-11  Glenn Morris  <address@hidden>
 
        * debugging.texi (Error Debugging): Mention debug-on-message.
+       (Using Debugger): Mention debugger-bury-or-kill.
 
        * control.texi (Signaling Errors):
        * debugging.texi (Error Debugging):

=== modified file 'doc/lispref/debugging.texi'
--- a/doc/lispref/debugging.texi        2012-11-11 00:58:51 +0000
+++ b/doc/lispref/debugging.texi        2012-11-11 01:16:25 +0000
@@ -322,6 +322,7 @@
 as the error message and associated data, if it was invoked due to an
 error).
 
address@hidden debugger-bury-or-kill
   The backtrace buffer is read-only and uses a special major mode,
 Debugger mode, in which letters are defined as debugger commands.  The
 usual Emacs editing commands are available; thus, you can switch windows
@@ -330,8 +331,12 @@
 the debugger is a recursive editing level (@pxref{Recursive Editing})
 and it is wise to go back to the backtrace buffer and exit the debugger
 (with the @kbd{q} command) when you are finished with it.  Exiting
-the debugger gets out of the recursive edit and kills the backtrace
-buffer.
+the debugger gets out of the recursive edit and buries the backtrace
+buffer.  (You can customize what the @kbd{q} command does with the
+backtrace buffer by setting the variable @code{debugger-bury-or-kill}.
+For example, set it to @code{kill} if you prefer to kill the buffer
+rather than bury it.  Consult the variable's documentation for more
+possibilities.)
 
   When the debugger has been entered, the @code{debug-on-error}
 variable is temporarily set according to

=== modified file 'etc/NEWS'
--- a/etc/NEWS  2012-11-11 00:58:51 +0000
+++ b/etc/NEWS  2012-11-11 01:16:25 +0000
@@ -804,7 +804,9 @@
 *** New error type and new function `user-error'.
 These do not trigger the debugger.
 
-*** New option `debugger-bury-or-kill'.
++++
+*** New option `debugger-bury-or-kill', saying what to do with the
+debugger buffer when exiting debug.
 
 +++
 *** Set `debug-on-message' to enter the debugger when a certain

=== modified file 'lisp/ChangeLog'
--- a/lisp/ChangeLog    2012-11-11 00:43:54 +0000
+++ b/lisp/ChangeLog    2012-11-11 01:16:25 +0000
@@ -1,5 +1,7 @@
 2012-11-11  Glenn Morris  <address@hidden>
 
+       * emacs-lisp/debug.el (debugger-bury-or-kill): Doc tweak.
+
        * help.el (temp-buffer-max-height):
        * window.el (fit-frame-to-buffer, fit-frame-to-buffer-bottom-margin):
        * emacs-lisp/debug.el (debugger-bury-or-kill): Fix :version.

=== modified file 'lisp/emacs-lisp/debug.el'
--- a/lisp/emacs-lisp/debug.el  2012-11-11 00:40:37 +0000
+++ b/lisp/emacs-lisp/debug.el  2012-11-11 01:16:25 +0000
@@ -49,9 +49,9 @@
   :version "21.1")
 
 (defcustom debugger-bury-or-kill 'bury
-  "How to proceed with the debugger buffer when exiting `debug'.
-The value used here affects the behavior of operations on any
-window previously showing the debugger buffer.
+  "What to do with the debugger buffer when exiting `debug'.
+The value affects the behavior of operations on any window
+previously showing the debugger buffer.
 
 `nil' means that if its window is not deleted when exiting the
   debugger, invoking `switch-to-prev-buffer' will usually show