* doc/lispref/debugging.texi (Error Debugging): Mention debug-on-message.

* etc/NEWS: Related markup.

diff --git a/doc/lispref/ChangeLog b/doc/lispref/ChangeLog
index bc48f74401fd033af5e4b6e06a5d48a1bda3a9ec..0016258bcb5b6b8662d8eb4f09f1008d884fd9bb 100644 (file)
--- a/doc/lispref/ChangeLog
+++ b/doc/lispref/ChangeLog
@@ -1,5 +1,7 @@
 2012-11-11  Glenn Morris  <rgm@gnu.org>
 
+       * debugging.texi (Error Debugging): Mention debug-on-message.
+
        * control.texi (Signaling Errors):
        * debugging.texi (Error Debugging):
        * errors.texi (Standard Errors): Add user-error.

diff --git a/doc/lispref/debugging.texi b/doc/lispref/debugging.texi
index 74000c2ba66483fab68b6448d8cce7c821c2f4b1..9a43cfeac5d3ac4c81234406f249a4061cc29498 100644 (file)
--- a/doc/lispref/debugging.texi
+++ b/doc/lispref/debugging.texi
@@ -163,6 +163,14 @@ supported values correspond to the signals @code{SIGUSR1} and
 @code{inhibit-quit} is set and Emacs is not otherwise responding.
 @end defopt
 
+@cindex message, finding what causes a particular message
+@defvar 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.
+@end 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

diff --git a/etc/NEWS b/etc/NEWS
index 6ab23a4239d89ca069aa00f012aaee9eb1af9cde..42c639ef25bd4d088a67a62ed6b7b85c5d920ac7 100644 (file)
--- a/etc/NEWS
+++ b/etc/NEWS
@@ -806,6 +806,7 @@ These do not trigger the debugger.
 
 *** 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.