From: Thomas Wolff <towo@towo.net>
To: cygwin@cygwin.com
Subject: Re: cygwin 3.1 pseudo console in PTY and break/ctrl-c handling
Date: Tue, 18 Feb 2020 22:54:00 -0000 [thread overview]
Message-ID: <b579ee20-ff91-b633-594f-d7dee81936f8@towo.net> (raw)
In-Reply-To: <937489593.4978154.1582060605719@mail.yahoo.com>
Am 18.02.2020 um 22:16 schrieb Kevin Schnitzius via cygwin:
> With Cygwin version 3.0.7-1, crtl-c kills native apps that are started from the shell, For example, starting notepad in the foreground from bash would be kill by a ctrl-c.
>
> With Cygwin version 3.1.2-1, crtl-c DOES NOT kill native apps that are started from the shell,
>
> Can I restore this behavior?
>
> With 3.1.2-1:
>
> mintty -o "CA+F12:break"Â Â Â Â Â Â Â Â =====>Â Â ctrl-alt-F12 causes a break and kills notepad
> mintty -o "c:break"Â Â Â Â Â Â Â Â Â Â =====>Â Â ctrl-shift-c causes a break and kills notepad
> mintty -o "C+c:break"Â Â Â Â Â Â Â Â Â =====>Â FAIL -- ctrl-c kills native apps but notepad is not affected
> mintty -o "CA+c:break"Â Â Â Â Â Â Â Â Â =====>Â FAIL -- ctrl-alt-c kills native apps but notepad is not affected
This would be mintty -o KeyFunctions='CA+F12:break' etc.
The latter two are not valid mintty configuration; Ctrl is only
supported as a modifier for function keys and special keys, not letters.
This is unchanged with the cygwin version.
> These tests show that the 'break' signal can be propagated from mintty but is not for the ctrl-c case.
>
> I am guessing that this behavior is from the pty handing but I have not dug into this code or installed winpty.
>
> Is all this documented somewhere that I could not find?
>
> Kevin
>
> --
> Problem reports: http://cygwin.com/problems.html
> FAQ: http://cygwin.com/faq/
> Documentation: http://cygwin.com/docs.html
> Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
>
--
Problem reports: http://cygwin.com/problems.html
FAQ: http://cygwin.com/faq/
Documentation: http://cygwin.com/docs.html
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
next prev parent reply other threads:[~2020-02-18 22:54 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <937489593.4978154.1582060605719.ref@mail.yahoo.com>
2020-02-18 21:18 ` Kevin Schnitzius via cygwin
2020-02-18 21:30 ` Jose Isaias Cabrera
2020-02-18 22:54 ` Thomas Wolff [this message]
2020-02-19 20:02 ` Kevin Schnitzius via cygwin
2020-02-19 20:21 ` Brian Inglis
2020-02-20 9:11 ` Thomas Wolff
2020-02-20 0:32 ` Takashi Yano
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=b579ee20-ff91-b633-594f-d7dee81936f8@towo.net \
--to=towo@towo.net \
--cc=cygwin@cygwin.com \
/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.
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).