From 754bbf7a25a8dda49b5d08ef0d0443bbf5af0e36 Mon Sep 17 00:00:00 2001 From: Craig Jennings Date: Sun, 7 Apr 2024 13:41:34 -0500 Subject: new repository --- devdocs/elisp/explicit-debug.html | 6 ++++++ 1 file changed, 6 insertions(+) create mode 100644 devdocs/elisp/explicit-debug.html (limited to 'devdocs/elisp/explicit-debug.html') diff --git a/devdocs/elisp/explicit-debug.html b/devdocs/elisp/explicit-debug.html new file mode 100644 index 00000000..505342f6 --- /dev/null +++ b/devdocs/elisp/explicit-debug.html @@ -0,0 +1,6 @@ +

Explicit Entry to the Debugger

You can cause the debugger to be called at a certain point in your program by writing the expression (debug) at that point. To do this, visit the source file, insert the text ‘(debug)’ at the proper place, and type C-M-x (eval-defun, a Lisp mode key binding). Warning: if you do this for temporary debugging purposes, be sure to undo this insertion before you save the file!

The place where you insert ‘(debug)’ must be a place where an additional form can be evaluated and its value ignored. (If the value of (debug) isn’t ignored, it will alter the execution of the program!) The most common suitable places are inside a progn or an implicit progn (see Sequencing).

If you don’t know exactly where in the source code you want to put the debug statement, but you want to display a backtrace when a certain message is displayed, you can set debug-on-message to a regular expression matching the desired message.

+

+ Copyright © 1990-1996, 1998-2022 Free Software Foundation, Inc.
Licensed under the GNU GPL license.
+ https://www.gnu.org/software/emacs/manual/html_node/elisp/Explicit-Debug.html +

+
-- cgit v1.2.3