From: Ken Brown <kbrown@cornell.edu>
To: Eli Zaretskii <eliz@gnu.org>
Cc: eggert@cs.ucla.edu, 51820-done@debbugs.gnu.org
Subject: bug#51820: 29.0.50; process_pending_signals is almost useless without SIGIO
Date: Wed, 17 Nov 2021 13:11:06 -0500 [thread overview]
Message-ID: <c030d4b3-4723-0fe5-9d67-9fc668e62698@cornell.edu> (raw)
In-Reply-To: <83ilwvw7vy.fsf@gnu.org>
On 11/14/2021 1:48 AM, Eli Zaretskii wrote:
>> Date: Sat, 13 Nov 2021 18:25:55 -0500
>> Cc: 51820@debbugs.gnu.org, Eli Zaretskii <eliz@gnu.org>
>> From: Ken Brown <kbrown@cornell.edu>
>>
>>> In that case, perhaps someone using Cygwin (i.e., not me) could look into this.
>>> Evidently it has not been much of a practical problem all these years.
>>
>> It's hard to know whether it's been a problem. Maybe emacs would be more
>> responsive to C-g on Cygwin if we removed the #ifdef from handle_async_input.
>> My preference would be to try that (on master of course) and see if anything breaks.
>>
>> Eli, WDYT?
>
> Sure, feel free to install such a change on master.
Done.
> I don't know how
> many Cygwin users track the Emacs master branch, but if there are more
> than a couple, perhaps even provide a variable exposed to Lisp that
> users could tweak to see the result without rebuilding and without
> leaving the session.
Good idea. I think I'll wait a couple weeks so that I can see how the change
works myself, as well as to see if anyone notices. But then I might do that.
For now I'm closing the bug.
Ken
prev parent reply other threads:[~2021-11-17 18:11 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-11-13 22:49 bug#51820: 29.0.50; process_pending_signals is almost useless without SIGIO Ken Brown
2021-11-13 23:12 ` Paul Eggert
2021-11-13 23:17 ` Ken Brown
2021-11-13 23:18 ` Paul Eggert
2021-11-13 23:25 ` Ken Brown
2021-11-14 2:26 ` Lars Ingebrigtsen
2021-11-14 16:09 ` Ken Brown
2021-11-14 6:47 ` Eli Zaretskii
2021-11-17 18:11 ` Ken Brown [this message]
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=c030d4b3-4723-0fe5-9d67-9fc668e62698@cornell.edu \
--to=kbrown@cornell.edu \
--cc=51820-done@debbugs.gnu.org \
--cc=eggert@cs.ucla.edu \
--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).