all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: Spencer Baugh <sbaugh@janestreet.com>
Cc: 63096@debbugs.gnu.org
Subject: bug#63096: [PATCH] Note that Emacs pauses when handling sentinel errors
Date: Thu, 27 Apr 2023 08:35:21 +0300	[thread overview]
Message-ID: <838redubty.fsf@gnu.org> (raw)
In-Reply-To: <ierzg6u47xm.fsf@janestreet.com> (message from Spencer Baugh on Wed, 26 Apr 2023 18:04:05 -0400)

> From: Spencer Baugh <sbaugh@janestreet.com>
> Date: Wed, 26 Apr 2023 18:04:05 -0400
> 
> For emacs-29, since this variable is new in Emacs 29.

Thanks.

> diff --git a/doc/lispref/processes.texi b/doc/lispref/processes.texi
> index 50e67475d8e..39d1ee64e43 100644
> --- a/doc/lispref/processes.texi
> +++ b/doc/lispref/processes.texi
> @@ -2159,7 +2159,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}.  Additionally, Emacs pauses for

Why "Additionally"?  What you are describing is not in addition to
what was described before that.

> +@var{process-error-pause-time} seconds so that the user sees the
> +error.  @xref{Asynchronous Processes}

If we are mentioning this variable here, let's also mention it where
filter functions are described, since it is also relevant to those.





  reply	other threads:[~2023-04-27  5:35 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 [this message]
2023-05-02 14:46   ` sbaugh
2023-05-02 15:01     ` Robert Pluim
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=838redubty.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=63096@debbugs.gnu.org \
    --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.