From 47a73eb0718124dd26dfb656d3971080eaea0aa5 Mon Sep 17 00:00:00 2001 From: Glenn Morris Date: Thu, 13 Feb 2014 00:26:01 -0800 Subject: [PATCH] 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. --- doc/lispref/ChangeLog | 4 ++++ doc/lispref/debugging.texi | 6 +++--- etc/NEWS | 15 ++++++++------- lisp/ChangeLog | 4 ++++ lisp/jit-lock.el | 4 +++- 5 files changed, 22 insertions(+), 11 deletions(-) diff --git a/doc/lispref/ChangeLog b/doc/lispref/ChangeLog index c304cac04ba..f10577faf77 100644 --- a/doc/lispref/ChangeLog +++ b/doc/lispref/ChangeLog @@ -1,3 +1,7 @@ +2014-02-13 Glenn Morris + + * debugging.texi (Debugger Commands): Tiny edits. + 2014-02-12 Glenn Morris * package.texi (Simple Packages): Describe URL and Keywords headers. diff --git a/doc/lispref/debugging.texi b/doc/lispref/debugging.texi index 774ac594e0d..a9d0c1c4ed0 100644 --- a/doc/lispref/debugging.texi +++ b/doc/lispref/debugging.texi @@ -425,7 +425,8 @@ Flag the current frame like @kbd{b}. Then continue execution like 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 @@ function and thus cancel the effect of @code{debug-on-entry}, it may 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 diff --git a/etc/NEWS b/etc/NEWS index e93376214bf..b82dc63bec0 100644 --- a/etc/NEWS +++ b/etc/NEWS @@ -357,15 +357,16 @@ Also the following files used by the now obsolete otodo-mode.el: ** 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 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' lets you use the debuggers on -code run via JIT Lock. +--- +*** 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. diff --git a/lisp/ChangeLog b/lisp/ChangeLog index d5c0f6aa552..afbaec909c6 100644 --- a/lisp/ChangeLog +++ b/lisp/ChangeLog @@ -1,3 +1,7 @@ +2014-02-13 Glenn Morris + + * jit-lock.el (jit-lock-mode): Doc fix. + 2014-02-13 Juanma Barranquero * apropos.el (apropos-read-pattern): When the user passes an empty diff --git a/lisp/jit-lock.el b/lisp/jit-lock.el index 9f60ecb0126..42e6519e38c 100644 --- a/lisp/jit-lock.el +++ b/lisp/jit-lock.el @@ -189,7 +189,9 @@ following ways: 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) -- 2.39.2