[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[Emacs-diffs] emacs-26 5dd0e5c: Mention trace.el facilities in the ELisp
From: |
Eli Zaretskii |
Subject: |
[Emacs-diffs] emacs-26 5dd0e5c: Mention trace.el facilities in the ELisp manual |
Date: |
Sat, 13 Jan 2018 06:54:50 -0500 (EST) |
branch: emacs-26
commit 5dd0e5c54d29e81c07798a124295c8c3f016d621
Author: Eli Zaretskii <address@hidden>
Commit: Eli Zaretskii <address@hidden>
Mention trace.el facilities in the ELisp manual
* doc/lispref/debugging.texi (Debugging): Mention the trace.el
library.
---
doc/lispref/debugging.texi | 10 ++++++++++
1 file changed, 10 insertions(+)
diff --git a/doc/lispref/debugging.texi b/doc/lispref/debugging.texi
index cb6f6e9..fbc5238 100644
--- a/doc/lispref/debugging.texi
+++ b/doc/lispref/debugging.texi
@@ -20,6 +20,16 @@ alter its internal state.
You can use Edebug, a source-level debugger for Emacs Lisp.
@item
address@hidden tracing Lisp programs
+You can trace the execution of functions involved in the problem using
+the tracing facilities provided by the @file{trace.el} package. This
+package provides the functions @code{trace-function-foreground} and
address@hidden for tracing function calls, and
address@hidden for adding values of select variables to the
+trace. For the details, see the documentation of these facilities in
address@hidden
+
address@hidden
If a syntactic problem is preventing Lisp from even reading the
program, you can locate it using Lisp editing commands.
[Prev in Thread] |
Current Thread |
[Next in Thread] |
- [Emacs-diffs] emacs-26 5dd0e5c: Mention trace.el facilities in the ELisp manual,
Eli Zaretskii <=