From: Ken Brown <kbrown@cornell.edu>
To: Lars Ingebrigtsen <larsi@gnus.org>
Cc: 50043@debbugs.gnu.org
Subject: bug#50043: 28.0.50; USABLE_SIGOI undef code paths do not work correctly
Date: Wed, 17 Nov 2021 09:25:30 -0500 [thread overview]
Message-ID: <65f67100-2256-ee0d-4722-6d0e7e7e9cd5@cornell.edu> (raw)
In-Reply-To: <87mtm3p6uk.fsf@gnus.org>
On 11/17/2021 2:41 AM, Lars Ingebrigtsen wrote:
> Ken Brown <kbrown@cornell.edu> writes:
>
>> Namely, whenever wait_reading_process_output is polling for input,
>> avoid getting stuck in select, something like this:
>
> [...]
>
>> +#ifndef USABLE_SIGIO
>> + /* If we're polling for input, don't get stuck in select for
>> + more than 25 msec. */
>> + struct timespec short_timeout = make_timespec (0, 25000000);
>> + if ((read_kbd || !NILP (wait_for_cell))
>> + && timespec_cmp (short_timeout, timeout) < 0)
>> + timeout = short_timeout;
>> +#endif
>
> Sounds like a good general solution to me (but I guess this will also
> affect `accept-process-output'? So it should probably be documented
> there).
I don't think it affects accept-process-output. When the latter calls
wait_reading_process_output, read_kbd == 0 and wait_for_cell == Qnil.
Ken
next prev parent reply other threads:[~2021-11-17 14:25 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-08-13 11:56 bug#50043: 28.0.50; USABLE_SIGOI undef code paths do not work correctly Lars Ingebrigtsen
2021-08-13 13:16 ` Eli Zaretskii
2021-08-13 14:31 ` Lars Ingebrigtsen
2021-08-13 15:51 ` Eli Zaretskii
2021-08-14 11:52 ` Lars Ingebrigtsen
2021-11-15 15:19 ` Ken Brown
2021-11-15 17:24 ` Eli Zaretskii
2021-11-15 19:26 ` Ken Brown
2021-11-16 17:44 ` Eli Zaretskii
2021-11-16 23:06 ` Ken Brown
2021-11-17 7:41 ` Lars Ingebrigtsen
2021-11-17 14:25 ` Ken Brown [this message]
2021-11-17 13:14 ` Eli Zaretskii
2021-11-17 14:19 ` Ken Brown
2021-11-17 14:34 ` Eli Zaretskii
2021-11-17 14:59 ` Ken Brown
2021-11-17 16:56 ` Eli Zaretskii
2021-11-17 17:25 ` Ken Brown
2021-11-17 17:37 ` Eli Zaretskii
2021-11-17 17:45 ` Ken Brown
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=65f67100-2256-ee0d-4722-6d0e7e7e9cd5@cornell.edu \
--to=kbrown@cornell.edu \
--cc=50043@debbugs.gnu.org \
--cc=larsi@gnus.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).