all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: Ken Brown <kbrown@cornell.edu>
Cc: 51820@debbugs.gnu.org, eggert@cs.ucla.edu
Subject: bug#51820: 29.0.50; process_pending_signals is almost useless without SIGIO
Date: Sun, 14 Nov 2021 08:47:45 +0200	[thread overview]
Message-ID: <83ilwvw7vy.fsf@gnu.org> (raw)
In-Reply-To: <a39f654c-a705-a900-c026-3b88d51d9dd6@cornell.edu> (message from Ken Brown on Sat, 13 Nov 2021 18:25:55 -0500)

> 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.  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.

Thanks.





  parent reply	other threads:[~2021-11-14  6:47 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 [this message]
2021-11-17 18:11           ` 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

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=83ilwvw7vy.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=51820@debbugs.gnu.org \
    --cc=eggert@cs.ucla.edu \
    --cc=kbrown@cornell.edu \
    /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.