From 82ba818ff456bcd6d56a06226e3f27e98fbb55c3 Mon Sep 17 00:00:00 2001 From: Craig Jennings Date: Thu, 14 Aug 2025 22:58:58 -0500 Subject: removing all downloaded devdocs files --- devdocs/elisp/source-breakpoints.html | 12 ------------ 1 file changed, 12 deletions(-) delete mode 100644 devdocs/elisp/source-breakpoints.html (limited to 'devdocs/elisp/source-breakpoints.html') diff --git a/devdocs/elisp/source-breakpoints.html b/devdocs/elisp/source-breakpoints.html deleted file mode 100644 index 64b894a2..00000000 --- a/devdocs/elisp/source-breakpoints.html +++ /dev/null @@ -1,12 +0,0 @@ -

Source Breakpoints

All breakpoints in a definition are forgotten each time you reinstrument it. If you wish to make a breakpoint that won’t be forgotten, you can write a source breakpoint, which is simply a call to the function edebug in your source code. You can, of course, make such a call conditional. For example, in the fac function, you can insert the first line as shown below, to stop when the argument reaches zero: 

(defun fac (n)
-  (if (= n 0) (edebug))
-  (if (< 0 n)
-      (* n (fac (1- n)))
-    1))
-
-

When the fac definition is instrumented and the function is called, the call to edebug acts as a breakpoint. Depending on the execution mode, Edebug stops or pauses there.

If no instrumented code is being executed when edebug is called, that function calls debug.

-

- 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/Source-Breakpoints.html -

-
-- cgit v1.2.3