[Emacs-diffs] /srv/bzr/emacs/emacs-24 r110838: * doc/lispref/debugging.texi (Error Debugging): Mention debug-on-message.

[Glenn Morris]

------------------------------------------------------------
revno: 110838
committer: Glenn Morris <address@hidden>
branch nick: emacs-24
timestamp: Sat 2012-11-10 16:58:51 -0800
message:
  * doc/lispref/debugging.texi (Error Debugging): Mention debug-on-message.
  
  * etc/NEWS: Related markup.
modified:
  doc/lispref/ChangeLog
  doc/lispref/debugging.texi
  etc/NEWS

=== modified file 'doc/lispref/ChangeLog'
--- a/doc/lispref/ChangeLog     2012-11-11 00:37:40 +0000
+++ b/doc/lispref/ChangeLog     2012-11-11 00:58:51 +0000
@@ -1,5 +1,7 @@
 2012-11-11  Glenn Morris  <address@hidden>
 
+       * debugging.texi (Error Debugging): Mention debug-on-message.
+
        * control.texi (Signaling Errors):
        * debugging.texi (Error Debugging):
        * errors.texi (Standard Errors): Add user-error.

=== modified file 'doc/lispref/debugging.texi'
--- a/doc/lispref/debugging.texi        2012-11-11 00:37:40 +0000
+++ b/doc/lispref/debugging.texi        2012-11-11 00:58:51 +0000
@@ -163,6 +163,14 @@
 @code{inhibit-quit} is set and Emacs is not otherwise responding.
 @end defopt
 
address@hidden message, finding what causes a particular message
address@hidden debug-on-message
+If you set @code{debug-on-message} to a regular expression,
+Emacs will enter the debugger if it displays a matching message in the
+echo area.  For example, this can be useful when trying to find the
+cause of a particular message.
address@hidden defvar
+
   To debug an error that happens during loading of the init
 file, use the option @samp{--debug-init}.  This binds
 @code{debug-on-error} to @code{t} while loading the init file, and

=== modified file 'etc/NEWS'
--- a/etc/NEWS  2012-11-11 00:37:40 +0000
+++ b/etc/NEWS  2012-11-11 00:58:51 +0000
@@ -806,6 +806,7 @@
 
 *** New option `debugger-bury-or-kill'.
 
++++
 *** Set `debug-on-message' to enter the debugger when a certain
 message is displayed in the echo area.  This can be useful when trying
 to work out which code is doing something.