[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
master 47c424f5ec8 1/5: Merge from origin/emacs-29
From: |
Dmitry Gutov |
Subject: |
master 47c424f5ec8 1/5: Merge from origin/emacs-29 |
Date: |
Fri, 5 May 2023 21:00:31 -0400 (EDT) |
branch: master
commit 47c424f5ec838c584d67adb3cc94d68b62996f8a
Merge: 1ef219e220c fceaf230b06
Author: Dmitry Gutov <dmitry@gutov.dev>
Commit: Dmitry Gutov <dmitry@gutov.dev>
Merge from origin/emacs-29
fceaf230b06 Note that Emacs pauses when handling sentinel errors
---
doc/lispref/processes.texi | 8 ++++++--
1 file changed, 6 insertions(+), 2 deletions(-)
diff --git a/doc/lispref/processes.texi b/doc/lispref/processes.texi
index 50e67475d8e..c901215d35d 100644
--- a/doc/lispref/processes.texi
+++ b/doc/lispref/processes.texi
@@ -1755,7 +1755,9 @@ caught automatically, so that it doesn't stop the
execution of whatever
program was running when the filter function was started. However, if
@code{debug-on-error} is non-@code{nil}, errors are not caught.
This makes it possible to use the Lisp debugger to debug filter
-functions. @xref{Debugger}.
+functions. @xref{Debugger}. If an error is caught, Emacs pauses for
+@code{process-error-pause-time} seconds so that the user sees the
+error. @xref{Asynchronous Processes}
Many filter functions sometimes (or always) insert the output in the
process's buffer, mimicking the actions of the default filter.
@@ -2159,7 +2161,9 @@ automatically, so that it doesn't stop the execution of
whatever
programs was running when the sentinel was started. However, if
@code{debug-on-error} is non-@code{nil}, errors are not caught.
This makes it possible to use the Lisp debugger to debug the
-sentinel. @xref{Debugger}.
+sentinel. @xref{Debugger}. If an error is caught, Emacs pauses for
+@code{process-error-pause-time} seconds so that the user sees the
+error. @xref{Asynchronous Processes}
While a sentinel is running, the process sentinel is temporarily
set to @code{nil} so that the sentinel won't run recursively.