new repository

1 files changed, 6 insertions, 0 deletions

diff --git a/devdocs/elisp/global-break-condition.html b/devdocs/elisp/global-break-condition.html
new file mode 100644
index 00000000..5d0160a4
--- /dev/null
+++ b/devdocs/elisp/global-break-condition.html
@@ -0,0 +1,6 @@
+ <h4 class="subsubsection">Global Break Condition</h4>   <p>A <em>global break condition</em> 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-<code>nil</code> 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. </p>  <p>The condition expression is stored in <code>edebug-global-break-condition</code>. You can specify a new expression using the <kbd>X</kbd> command from the source code buffer while Edebug is active, or using <kbd>C-x X X</kbd> from any buffer at any time, as long as Edebug is loaded (<code>edebug-set-global-break-condition</code>). </p> <p>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 <code>nil</code> when not using it. </p><div class="_attribution">
+  <p class="_attribution-p">
+    Copyright &copy; 1990-1996, 1998-2022 Free Software Foundation, Inc. <br>Licensed under the GNU GPL license.<br>
+    <a href="https://www.gnu.org/software/emacs/manual/html_node/elisp/Global-Break-Condition.html" class="_attribution-link">https://www.gnu.org/software/emacs/manual/html_node/elisp/Global-Break-Condition.html</a>
+  </p>
+</div>