From: Stefan Kangas <stefankangas@gmail.com>
To: Katsumi Yamaoka <yamaoka@jpl.org>
Cc: 14553@debbugs.gnu.org, Daniel Colascione <dancol@dancol.org>
Subject: bug#14553: [cygwin] C-g doesn't interrupt (while t)
Date: Wed, 10 Jan 2024 03:14:11 -0800 [thread overview]
Message-ID: <CADwFkmkLozFp9jzJ2taunK7fVtWuiXAiYwLOFfQT-j9tPJRaLA@mail.gmail.com> (raw)
In-Reply-To: <CADwFkmk7t8ahz-Q8-0vSGjLxh_53CC5b44xnMq+ML7S8HZ4bnQ@mail.gmail.com> (Stefan Kangas's message of "Tue, 1 Oct 2019 02:59:51 +0200")
Daniel Colascione <dancol@dancol.org> writes:
> Sounds like a problem with signal delivery. Have you reported it to the
> cygwin mailing list?
Stefan Kangas <stefankangas@gmail.com> writes:
> Katsumi Yamaoka <yamaoka@jpl.org> writes:
>
>> > That was six years ago. Are you still seeing this on a modern version
>> > of Emacs?
>>
>> C-g still doesn't break (while t) on Emacs 27.0.50 of today, and
>> also on 26.3.50, 26.1, 25.1 rebuilt recently. I got used to it,
>> so I'm not so troubled. ;-) Thanks for following this up.
>
> Thanks for reporting back.
>
> Daniel Colascione suggested that there might be a problem with signal
> delivery on Cygwin, and to report it to their mailing list:
> https://debbugs.gnu.org/cgi/bugreport.cgi?bug=14553#20
>
> Perhaps that might be worth doing if you haven't already.
Coming back to this four years later, it sounds like this might be a bug
in Cygwin. Is that correct?
If yes, should we really keep this bug open on our end?
next prev parent reply other threads:[~2024-01-10 11:14 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-06-04 6:10 bug#14553: 24.3.50; C-g doesn't break inf-loop Katsumi Yamaoka
2013-07-02 20:12 ` Ken Brown
2013-07-02 23:17 ` Josh
2013-07-03 0:34 ` Katsumi Yamaoka
2013-07-03 11:13 ` Ken Brown
2014-03-23 6:27 ` Daniel Colascione
2019-09-30 15:44 ` Stefan Kangas
2019-10-01 0:01 ` Katsumi Yamaoka
2019-10-01 0:59 ` Stefan Kangas
2024-01-10 11:14 ` Stefan Kangas [this message]
2024-01-10 16:31 ` bug#14553: [cygwin] C-g doesn't interrupt (while t) Ken Brown
2024-01-10 17:09 ` Stefan Kangas
2024-01-11 5:29 ` Katsumi Yamaoka
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=CADwFkmkLozFp9jzJ2taunK7fVtWuiXAiYwLOFfQT-j9tPJRaLA@mail.gmail.com \
--to=stefankangas@gmail.com \
--cc=14553@debbugs.gnu.org \
--cc=dancol@dancol.org \
--cc=yamaoka@jpl.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).