[Emacs-diffs] trunk r116428: Small doc updates for debugging

[Glenn Morris]

------------------------------------------------------------
revno: 116428
revision-id: address@hidden
parent: address@hidden
committer: Glenn Morris <address@hidden>
branch nick: trunk
timestamp: Thu 2014-02-13 00:26:01 -0800
message:
  Small doc updates for debugging
  
  * doc/lispref/debugging.texi (Debugger Commands): Tiny edits.
  
  * lisp/jit-lock.el (jit-lock-mode): Doc fix.
  
  * etc/NEWS: Related edits.
modified:
  doc/lispref/ChangeLog          changelog-20091113204419-o5vbwnq5f7feedwu-6155
  doc/lispref/debugging.texi     
debugging.texi-20091113204419-o5vbwnq5f7feedwu-6171
  etc/NEWS                       news-20100311060928-aoit31wvzf25yr1z-1
  lisp/ChangeLog                 changelog-20091113204419-o5vbwnq5f7feedwu-1432
  lisp/jit-lock.el               jitlock.el-20091113204419-o5vbwnq5f7feedwu-1321

=== modified file 'doc/lispref/ChangeLog'
--- a/doc/lispref/ChangeLog     2014-02-13 02:19:48 +0000
+++ b/doc/lispref/ChangeLog     2014-02-13 08:26:01 +0000
@@ -1,3 +1,7 @@
+2014-02-13  Glenn Morris  <address@hidden>
+
+       * debugging.texi (Debugger Commands): Tiny edits.
+
 2014-02-12  Glenn Morris  <address@hidden>
 
        * package.texi (Simple Packages): Describe URL and Keywords headers.

=== modified file 'doc/lispref/debugging.texi'
--- a/doc/lispref/debugging.texi        2014-01-01 07:43:34 +0000
+++ b/doc/lispref/debugging.texi        2014-02-13 08:26:01 +0000
@@ -425,7 +425,8 @@
 are set up to do so by @code{debug-on-entry}.
 
 @item e
-Read a Lisp expression in the minibuffer, evaluate it, and print the
+Read a Lisp expression in the minibuffer, evaluate it (with the
+relevant lexical environment, if applicable), and print the
 value in the echo area.  The debugger alters certain important
 variables, and the current buffer, as part of its operation; @kbd{e}
 temporarily restores their values from outside the debugger, so you can
@@ -465,8 +466,7 @@
 erroneously show up in this list.
 
 @item v
-Display local variables (@pxref{Local Variables}) of the current stack
-frame.  Press @kbd{e} again to hide them.
+Toggle the display of local variables of the current stack frame.
 @end table
 
 @node Invoking the Debugger

=== modified file 'etc/NEWS'
--- a/etc/NEWS  2014-02-12 18:51:10 +0000
+++ b/etc/NEWS  2014-02-13 08:26:01 +0000
@@ -357,15 +357,16 @@
 
 ** Backtrace and debugger
 
-*** The Lisp debugger's `e' command now includes the lexical environment
-when evaluating the code in the context at point.  Hence, it now lets
-you access lexical variables.
-
 +++
-*** New command `v' (`debugger-toggle-locals') displays local vars.
-
-*** New minor mode `jit-lock-debug-mode' lets you use the debuggers on
-code run via JIT Lock.
+*** New Lisp debugger command `v' (`debugger-toggle-locals') toggles the
+displays of local variables.
+
+*** The Lisp debugger's `e' command (`debugger-eval-expression') now includes
+the lexical environment when evaluating the code in the context at point
+(and so allows you to access lexical variables).
+
+---
+*** New minor mode `jit-lock-debug-mode' helps you debug code run via JIT Lock.
 
 ---
 ** Battery information can now be retrieved from BSD's `apm' utility.

=== modified file 'lisp/ChangeLog'
--- a/lisp/ChangeLog    2014-02-13 05:23:06 +0000
+++ b/lisp/ChangeLog    2014-02-13 08:26:01 +0000
@@ -1,3 +1,7 @@
+2014-02-13  Glenn Morris  <address@hidden>
+
+       * jit-lock.el (jit-lock-mode): Doc fix.
+
 2014-02-13  Juanma Barranquero  <address@hidden>
 
        * apropos.el (apropos-read-pattern): When the user passes an empty

=== modified file 'lisp/jit-lock.el'
--- a/lisp/jit-lock.el  2014-02-13 03:29:47 +0000
+++ b/lisp/jit-lock.el  2014-02-13 08:26:01 +0000
@@ -189,7 +189,9 @@
 Stealth fontification only occurs while the system remains unloaded.
 If the system load rises above `jit-lock-stealth-load' percent, stealth
 fontification is suspended.  Stealth fontification intensity is controlled via
-the variable `jit-lock-stealth-nice'."
+the variable `jit-lock-stealth-nice'.
+
+If you need to debug code run from jit-lock, see `jit-lock-debug-mode'."
   (setq jit-lock-mode arg)
   (cond
    ((buffer-base-buffer)