From: sbaugh@catern.com
To: Robert Pluim <rpluim@gmail.com>
Cc: Spencer Baugh <sbaugh@janestreet.com>,
Eli Zaretskii <eliz@gnu.org>,
63096@debbugs.gnu.org
Subject: bug#63096: [PATCH] Note that Emacs pauses when handling sentinel errors
Date: Tue, 02 May 2023 15:38:54 +0000 (UTC) [thread overview]
Message-ID: <87wn1qpwtu.fsf@catern.com> (raw)
In-Reply-To: <874jouzsjg.fsf@gmail.com> (Robert Pluim's message of "Tue, 02 May 2023 17:01:23 +0200")
[-- Attachment #1: Type: text/plain, Size: 1198 bytes --]
Robert Pluim <rpluim@gmail.com> writes:
>>>>>> On Tue, 02 May 2023 14:46:22 +0000 (UTC), sbaugh@catern.com 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.
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #2: 0001-Note-that-Emacs-pauses-when-handling-sentinel-errors.patch --]
[-- Type: text/x-patch, Size: 1941 bytes --]
From 2d5fe79761683d3d6b84b3d9dacb1a997a7e19fc Mon Sep 17 00:00:00 2001
From: Spencer Baugh <sbaugh@catern.com>
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
next prev parent reply other threads:[~2023-05-02 15:38 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-04-26 22:04 bug#63096: [PATCH] Note that Emacs pauses when handling sentinel errors Spencer Baugh
2023-04-27 5:35 ` Eli Zaretskii
2023-05-02 14:46 ` sbaugh
2023-05-02 15:01 ` Robert Pluim
2023-05-02 15:38 ` sbaugh [this message]
2023-05-02 17:52 ` Eli Zaretskii
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://www.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87wn1qpwtu.fsf@catern.com \
--to=sbaugh@catern.com \
--cc=63096@debbugs.gnu.org \
--cc=eliz@gnu.org \
--cc=rpluim@gmail.com \
--cc=sbaugh@janestreet.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/emacs.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).