From: Robert Pluim <rpluim@gmail.com>
To: sbaugh@catern.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 17:01:23 +0200 [thread overview]
Message-ID: <874jouzsjg.fsf@gmail.com> (raw)
In-Reply-To: <878re6rdtu.fsf@catern.com> (sbaugh@catern.com's message of "Tue, 02 May 2023 14:46:22 +0000 (UTC)")
>>>>> 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
--
next prev parent reply other threads:[~2023-05-02 15:01 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 [this message]
2023-05-02 15:38 ` sbaugh
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=874jouzsjg.fsf@gmail.com \
--to=rpluim@gmail.com \
--cc=63096@debbugs.gnu.org \
--cc=eliz@gnu.org \
--cc=sbaugh@catern.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 external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.