From: "João Távora" <joaotavora@gmail.com>
To: Eli Zaretskii <eliz@gnu.org>
Cc: 32986@debbugs.gnu.org
Subject: bug#32986: 27.0.50; unexpected delay in while-no-input + accept-process-output
Date: Tue, 9 Oct 2018 09:47:58 +0100 [thread overview]
Message-ID: <CALDnm52miiyS94xRYXjg+cD_AOgb_j6A72RPCayxYYcPkR4eag@mail.gmail.com> (raw)
In-Reply-To: <83h8hvzw70.fsf@gnu.org>
[-- Attachment #1: Type: text/plain, Size: 805 bytes --]
On Tue, Oct 9, 2018, 03:32 Eli Zaretskii <eliz@gnu.org> wrote:
> > From: João Távora <joaotavora@gmail.com>
> > Date: Mon, 8 Oct 2018 21:39:53 +0100
> > Cc: 32986@debbugs.gnu.org
> >
> > Thank you for the clarification. I have now read the original
> explanation, and it makes sense. Ultimately, I think
> > the sit-for is the right approach for my wait-for-any-process-or-input
> problem. Am I right to assume it's not
> > affected by your explanation, and that I can expect immediate return
> there?
>
> sit-for waits for keyboard input, so yes, it should return once the
> user presses some key.
>
Right. A final question: process input is also considered during the
sit-for, meaning a filter can throw to an enclosing tag and end it
prematurely and immediately, right?
>
[-- Attachment #2: Type: text/html, Size: 1455 bytes --]
next prev parent reply other threads:[~2018-10-09 8:47 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-10-08 10:48 bug#32986: 27.0.50; unexpected delay in while-no-input + accept-process-output João Távora
2018-10-08 15:05 ` Eli Zaretskii
2018-10-08 20:06 ` João Távora
2018-10-08 20:25 ` Eli Zaretskii
2018-10-08 20:39 ` João Távora
2018-10-09 2:32 ` Eli Zaretskii
2018-10-09 8:47 ` João Távora [this message]
2018-10-09 15:01 ` Eli Zaretskii
2018-10-14 22:08 ` João Távora
2018-10-15 15:03 ` Eli Zaretskii
2018-10-15 15:50 ` João Távora
2018-12-11 18:09 ` Dmitry Gutov
2018-12-12 21:42 ` João Távora
2018-12-12 23:51 ` Dmitry Gutov
2018-12-13 23:14 ` Dmitry Gutov
2020-09-11 16:22 ` Stefan Monnier
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=CALDnm52miiyS94xRYXjg+cD_AOgb_j6A72RPCayxYYcPkR4eag@mail.gmail.com \
--to=joaotavora@gmail.com \
--cc=32986@debbugs.gnu.org \
--cc=eliz@gnu.org \
/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).