Subject: bug#63096: [PATCH] Note that Emacs pauses when handling sentinel errors

From: [email-masked]
Date: Tue, 02 May 2023 15:38:54 +0000 (UTC)

Robert Pluim <[email-masked]> writes:

>>>>>> On Tue, 02 May 2023 14:46:22 +0000 (UTC), [email-masked] said:
>     sbaugh> +functions.  @xref{Debugger}.  If an error is caught, Emacs pauses for
>     sbaugh> +@var{process-error-pause-time} seconds so that the user sees the
>     sbaugh> +error.  @xref{Asynchronous Processes}
>
> @var{} is for formal parameters to functions (they end up
> upcased), but this is a variable, so you need @code{}
>
>     sbaugh>    Many filter functions sometimes (or always) insert the output in the
>     sbaugh>  process's buffer, mimicking the actions of the default filter.
>     sbaugh> @@ -2159,7 +2161,9 @@ Sentinels
>     sbaugh>  programs was running when the sentinel was started.  However, if
>     sbaugh>  @code{debug-on-error} is non-@code{nil},  errors are not caught.
>     sbaugh>  This makes it possible to use the Lisp debugger to debug the
>     sbaugh> -sentinel.  @xref{Debugger}.
>     sbaugh> +sentinel.  @xref{Debugger}.  If an error is caught, Emacs pauses for
>     sbaugh> +@var{process-error-pause-time} seconds so that the user sees the
>     sbaugh> +error.  @xref{Asynchronous Processes}
>
> Similarly here.
>
> Robert

Fixed.

>From 2d5fe79761683d3d6b84b3d9dacb1a997a7e19fc Mon Sep 17 00:00:00 2001
From: Spencer Baugh <[email-masked]>
Date: Tue, 2 May 2023 11:37:48 -0400
Subject: [PATCH] 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.
---
 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 @@ Filter Functions
 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 @@ Sentinels
 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.
-- 
2.38.0