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/global-break-condition.html | 6 ------ 1 file changed, 6 deletions(-) delete mode 100644 devdocs/elisp/global-break-condition.html (limited to 'devdocs/elisp/global-break-condition.html') diff --git a/devdocs/elisp/global-break-condition.html b/devdocs/elisp/global-break-condition.html deleted file mode 100644 index 5d0160a4..00000000 --- a/devdocs/elisp/global-break-condition.html +++ /dev/null @@ -1,6 +0,0 @@ -

Global Break Condition

A global break condition stops execution when a specified condition is satisfied, no matter where that may occur. Edebug evaluates the global break condition at every stop point; if it evaluates to a non-nil value, then execution stops or pauses depending on the execution mode, as if a breakpoint had been hit. If evaluating the condition gets an error, execution does not stop.

The condition expression is stored in edebug-global-break-condition. You can specify a new expression using the X command from the source code buffer while Edebug is active, or using C-x X X from any buffer at any time, as long as Edebug is loaded (edebug-set-global-break-condition).

The global break condition is the simplest way to find where in your code some event occurs, but it makes code run much more slowly. So you should reset the condition to nil when not using it.

-

- 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/Global-Break-Condition.html -

-
-- cgit v1.2.3