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

Document debugger-bury-or-kill

Browse source 
* 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.
This commit is contained in:
Glenn Morris 2012-11-10 17:16:25 -08:00
parent 164f28b577
commit 57fc0fee5f
5 changed files with 16 additions and 6 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

1
doc/lispref/ChangeLog
View file

@ -1,6 +1,7 @@
2012-11-11 Glenn Morris <rgm@gnu.org>
* debugging.texi (Error Debugging): Mention debug-on-message.
(Using Debugger): Mention debugger-bury-or-kill.
* control.texi (Signaling Errors):
* debugging.texi (Error Debugging):

9
doc/lispref/debugging.texi
View file

@ -322,6 +322,7 @@ is a message describing the reason that the debugger was invoked (such
as the error message and associated data, if it was invoked due to an
error).
@vindex 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 @@ switch buffers, visit files, or do any other sort of editing. However,
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

4
etc/NEWS
View file

@ -804,7 +804,9 @@ table, but with a different prefix.
*** 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

2
lisp/ChangeLog
View file

@ -1,5 +1,7 @@
2012-11-11 Glenn Morris <rgm@gnu.org>
* 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.

6
lisp/emacs-lisp/debug.el
View file

@ -49,9 +49,9 @@ the middle is discarded, and just the beginning and end are displayed."
: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