summaryrefslogtreecommitdiff
path: root/doc/lispref
diff options
context:
space:
mode:
authorEli Zaretskii <eliz@gnu.org>2023-11-17 14:28:13 +0200
committerEli Zaretskii <eliz@gnu.org>2023-11-17 14:28:13 +0200
commit232a57a3e32f8dc425887f6edda172255b265de3 (patch)
treea251a7719817a9cdd7a13006425495667a760aaa /doc/lispref
parentc65ddf26a335157b31d6a3d2cedffd661e7e42bf (diff)
downloademacs-232a57a3e32f8dc425887f6edda172255b265de3.tar.gz
emacs-232a57a3e32f8dc425887f6edda172255b265de3.tar.bz2
emacs-232a57a3e32f8dc425887f6edda172255b265de3.zip
; * doc/lispref/debugging.texi (Debugging): Add cross-references.
Diffstat (limited to 'doc/lispref')
-rw-r--r--doc/lispref/debugging.texi5
1 files changed, 3 insertions, 2 deletions
diff --git a/doc/lispref/debugging.texi b/doc/lispref/debugging.texi
index 4c1ad291876..57ed5806855 100644
--- a/doc/lispref/debugging.texi
+++ b/doc/lispref/debugging.texi
@@ -13,11 +13,12 @@ Lisp program.
@itemize @bullet
@item
If a problem occurs when you run the program, you can use the built-in
-Emacs Lisp debugger to suspend the Lisp evaluator, and examine and/or
-alter its internal state.
+Emacs Lisp debugger (@pxref{Debugger}) to suspend the Lisp evaluator,
+and examine and/or alter its internal state.
@item
You can use Edebug, a source-level debugger for Emacs Lisp.
+@xref{Edebug}.
@item
@cindex tracing Lisp programs