new repository

1 files changed, 8 insertions, 0 deletions

diff --git a/devdocs/elisp/checking-whether-to-stop.html b/devdocs/elisp/checking-whether-to-stop.html
new file mode 100644
index 00000000..4036d1a3
--- /dev/null
+++ b/devdocs/elisp/checking-whether-to-stop.html
@@ -0,0 +1,8 @@
+ <h4 class="subsubsection">Checking Whether to Stop</h4> <p>Whenever Edebug is entered, it needs to save and restore certain data before even deciding whether to make trace information or stop the program. </p> <ul> <li>  <code>max-lisp-eval-depth</code> (see <a href="eval">Eval</a>) and <code>max-specpdl-size</code> (see <a href="local-variables">Local Variables</a>) are both increased to reduce Edebug’s impact on the stack. You could, however, still run out of stack space when using Edebug. You can also enlarge the value of <code>edebug-max-depth</code> if Edebug reaches the limit of recursion depth instrumenting code that contains very large quoted lists. </li>
+<li> The state of keyboard macro execution is saved and restored. While Edebug is active, <code>executing-kbd-macro</code> is bound to <code>nil</code> unless <code>edebug-continue-kbd-macro</code> is non-<code>nil</code>. </li>
+</ul><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/Checking-Whether-to-Stop.html" class="_attribution-link">https://www.gnu.org/software/emacs/manual/html_node/elisp/Checking-Whether-to-Stop.html</a>
+  </p>
+</div>