From: Spencer Baugh Date: Tue, 2 May 2023 15:37:48 +0000 (-0400) Subject: Note that Emacs pauses when handling sentinel errors X-Git-Tag: emacs-29.0.91~64 X-Git-Url: http://git.eshelyaron.com/gitweb/?a=commitdiff_plain;h=fceaf230b063a0df9fb79cd5159cac4a761aba87;p=emacs.git Note that Emacs pauses when handling sentinel errors Noting this behavior and variable here makes it easier to understand the behavior of Emacs when a sentinel has an error. * doc/lispref/processes.texi (Filter Functions): Note that Emacs pauses when handling sentinel errors. (Sentinels): Note that Emacs pauses when handling sentinel errors. (Bug#63096) --- 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.