Commit c9832cd8 authored by Xue Fuqiao's avatar Xue Fuqiao
Browse files

Document `debugger-toggle-locals'.

* doc/lispref/debugging.texi (Debugger Commands): Document `debugger-toggle-locals'.
parent ced5cc29
2013-12-22 Xue Fuqiao <>
* debugging.texi (Debugger Commands): Document `debugger-toggle-locals'.
2013-12-21 Chong Yidong <>
* text.texi (Region Indent): Note the new interactive behavior of
......@@ -388,6 +388,7 @@ the same function. (To do this, visit the source for the function and
type @kbd{C-M-x} on its definition.) You cannot use the Lisp debugger
to step through a primitive function.
@c FIXME: Add @findex for the following commands? --xfq
Here is a list of Debugger mode commands:
@table @kbd
......@@ -462,6 +463,10 @@ This is a list of functions that are set to break on entry by means of
@code{debug-on-entry}. @strong{Warning:} if you redefine such a
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.
@end table
@node Invoking the Debugger
......@@ -304,7 +304,8 @@ Also the following files used by the now obsolete otodo-mode.el:
when evaluating the code in the context at point. Hence, it now lets
you access lexical variables.
*** New command `v' (`debuger-toggle-locals) displays local vars.
*** 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.
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