Commit 47a73eb0 authored by Glenn Morris's avatar Glenn Morris

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.
parent c9b6b262
2014-02-13 Glenn Morris <rgm@gnu.org>
* debugging.texi (Debugger Commands): Tiny edits.
2014-02-12 Glenn Morris <rgm@gnu.org>
* package.texi (Simple Packages): Describe URL and Keywords headers.
......
......@@ -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
......
......@@ -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.
......
2014-02-13 Glenn Morris <rgm@gnu.org>
* jit-lock.el (jit-lock-mode): Doc fix.
2014-02-13 Juanma Barranquero <lekktu@gmail.com>
* apropos.el (apropos-read-pattern): When the user passes an empty
......
......@@ -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)
......
Markdown is supported
0% or
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment