aboutsummaryrefslogtreecommitdiffstats
path: root/doc/lispref/debugging.texi
diff options
context:
space:
mode:
authorGemini Lasswell2018-08-01 07:47:12 -0700
committerGemini Lasswell2018-08-03 08:54:08 -0700
commit95b2ab3dccdc756614b4c8f45a7b206d61753705 (patch)
treef3fd4b5256aa6c6786d0ac4f80fb1d87dcc2e401 /doc/lispref/debugging.texi
parent58be6cb6bbb2cc7b1c35c0fc30b6f4f9b111eb77 (diff)
downloademacs-95b2ab3dccdc756614b4c8f45a7b206d61753705.tar.gz
emacs-95b2ab3dccdc756614b4c8f45a7b206d61753705.zip
Fix some documentation formatting nits
* doc/misc/ert.texi (Running Tests Interactively): Correct Elisp manual titile in xref. * doc/lispref/edebug.texi (Edebug Misc): Use single argument form of xref. * doc/lispref/debugging.texi (Backtraces): Add comma and period after xref braces. (Backtraces): Correct Emacs manual title. (Internals of Debugger): Add a space before period.
Diffstat (limited to 'doc/lispref/debugging.texi')
-rw-r--r--doc/lispref/debugging.texi10
1 files changed, 5 insertions, 5 deletions
diff --git a/doc/lispref/debugging.texi b/doc/lispref/debugging.texi
index 841b16eaf95..9b3ba6cf7ee 100644
--- a/doc/lispref/debugging.texi
+++ b/doc/lispref/debugging.texi
@@ -402,8 +402,8 @@ assumptions are false if the debugger is running interpreted.
402@cindex backtrace buffer 402@cindex backtrace buffer
403 403
404Debugger mode is derived from Backtrace mode, which is also used to 404Debugger mode is derived from Backtrace mode, which is also used to
405show backtraces by Edebug and ERT. (@pxref{Edebug} and @ref{Top,the 405show backtraces by Edebug and ERT. (@pxref{Edebug}, and @ref{Top,the
406ERT manual,, ert, ERT: Emacs Lisp Regression Testing}) 406ERT manual,, ert, ERT: Emacs Lisp Regression Testing}.)
407 407
408@cindex stack frame 408@cindex stack frame
409The backtrace buffer shows you the functions that are executing and 409The backtrace buffer shows you the functions that are executing and
@@ -423,9 +423,9 @@ source code is located. You can click with the mouse on that name, or
423move to it and type @key{RET}, to visit the source code. You can also 423move to it and type @key{RET}, to visit the source code. You can also
424type @key{RET} while point is on any name of a function or variable 424type @key{RET} while point is on any name of a function or variable
425which is not underlined, to see help information for that symbol in a 425which is not underlined, to see help information for that symbol in a
426help buffer, if any exists. The @code{xref-find-definitions} command, 426help buffer, if any exists. The @code{xref-find-definitions} command,
427bound to @key{M-.}, can also be used on any identifier in a backtrace 427bound to @key{M-.}, can also be used on any identifier in a backtrace
428(@pxref{Looking Up Identifiers,,,emacs,Emacs manual}). 428(@pxref{Looking Up Identifiers,,,emacs, The GNU Emacs Manual}).
429 429
430In backtraces, the tails of long lists and the ends of long strings, 430In backtraces, the tails of long lists and the ends of long strings,
431vectors or structures, as well as objects which are deeply nested, 431vectors or structures, as well as objects which are deeply nested,
@@ -690,7 +690,7 @@ Each line of the backtrace represents one function call. The line
690shows the function followed by a list of the values of the function's 690shows the function followed by a list of the values of the function's
691arguments if they are all known; if they are still being computed, the 691arguments if they are all known; if they are still being computed, the
692line consists of a list containing the function and its unevaluated 692line consists of a list containing the function and its unevaluated
693arguments. Long lists or deeply nested structures may be elided. 693arguments. Long lists or deeply nested structures may be elided.
694 694
695@smallexample 695@smallexample
696@group 696@group