cygwin 3.1 pseudo console in PTY and break/ctrl-c handling

cygwin 3.1 pseudo console in PTY and break/ctrl-c handling

[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

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

Re: cygwin 3.1 pseudo console in PTY and break/ctrl-c handling

[Jose Isaias Cabrera]

Kevin Schnitzius via cygwin, on Tuesday, February 18, 2020 04:16 PM,
> wrote...
>
> 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?

It's working fine for me,

$ uname -a
CYGWIN_NT-10.0-WOW HORSE8E 3.1.2(0.340/5/3) 2019-12-21 15:21 i686 Cygwin

But I am using a 32bit system. Or maybe, I am not properly following the steps you are doing.

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

Re: cygwin 3.1 pseudo console in PTY and break/ctrl-c handling

[Thomas Wolff]

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

Re: cygwin 3.1 pseudo console in PTY and break/ctrl-c handling

[Kevin Schnitzius via cygwin]

On Tuesday, February 18, 2020, 05:54:23 PM EST, Thomas Wolff <towo@towo.net> wrote: 

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

Ah, thank you.  That was the clue that I needed.

For those also having this problem:

mintty.exe -o "KeyFunctions=c:break" -o CtrlExchangeShift=true -

will propagate Ctrl-C to the non-native apps and kill them, imitating the behavior of 3.0.X Cygwin.

Now that I have played with this for a while, I am thinking that I like the new behavior better and I have assigned a new key to specifically kill native Windows programs instead letting the Ctrl-C do all the work (I am using Alt-F5 to do this).

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

Re: cygwin 3.1 pseudo console in PTY and break/ctrl-c handling

[Brian Inglis]

On 2020-02-19 13:02, Kevin Schnitzius via cygwin wrote:
> On Tuesday, February 18, 2020, 05:54:23 PM EST, Thomas Wolff wrote: 
>>> 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.
> 
> Ah, thank you.  That was the clue that I needed.
> 
> For those also having this problem:
> 
> mintty.exe -o "KeyFunctions=c:break" -o CtrlExchangeShift=true -
> 
> will propagate Ctrl-C to the non-native apps and kill them, imitating the behavior of 3.0.X Cygwin.
> 
> Now that I have played with this for a while, I am thinking that I like the new behavior better and I have assigned a new key to specifically kill native Windows programs instead letting the Ctrl-C do all the work (I am using Alt-F5 to do this).

Should the above settings not be the default behaviour for backward
compatibility and least surprise to users?

It used to be mintty just worked as expected with most programs, now additional
interfaces seem to be required depending on Windows versions, editions, and
releases. These helpers should either be included in the package, or be
dependencies pulled in by mintty without which it will not install, with the
appropriate interfaces installed and configured so that mintty, shells, and
programs run under it continue to work as expected.

-- 
Take care. Thanks, Brian Inglis, Calgary, Alberta, Canada

This email may be disturbing to some readers as it contains
too much technical detail. Reader discretion is advised.

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

Re: cygwin 3.1 pseudo console in PTY and break/ctrl-c handling

[Thomas Wolff]

On 19.02.2020 21:21, Brian Inglis wrote:
> On 2020-02-19 13:02, Kevin Schnitzius via cygwin wrote:
>> On Tuesday, February 18, 2020, 05:54:23 PM EST, Thomas Wolff wrote:
>>>> 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.
>> Ah, thank you.  That was the clue that I needed.
>>
>> For those also having this problem:
>>
>> mintty.exe -o "KeyFunctions=c:break" -o CtrlExchangeShift=true -
>>
>> will propagate Ctrl-C to the non-native apps and kill them, imitating the behavior of 3.0.X Cygwin.
>>
>> Now that I have played with this for a while, I am thinking that I like the new behavior better and I have assigned a new key to specifically kill native Windows programs instead letting the Ctrl-C do all the work (I am using Alt-F5 to do this).
> Should the above settings not be the default behaviour for backward
> compatibility and least surprise to users?
I was just taking up the requester's example. Sure ^C is an interrupt 
function on the command line. This is handled by the pty driver, not by 
the terminal.
The above configuration is a mintty feature of assigning functions (of 
which break is just one special case) to key combinations, independent 
of the stty settings.


> It used to be mintty just worked as expected with most programs, now additional
> interfaces seem to be required depending on Windows versions, editions, and
> releases. These helpers should either be included in the package, or be
> dependencies pulled in by mintty without which it will not install, with the
> appropriate interfaces installed and configured so that mintty, shells, and
> programs run under it continue to work as expected.
Some recently reported observations are related to the ConPTY project. 
There have been no changes in mintty concerning keyboard handling.

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

Re: cygwin 3.1 pseudo console in PTY and break/ctrl-c handling

[Takashi Yano]

On Tue, 18 Feb 2020 21:16:45 +0000 (UTC)
"Kevin Schnitzius via cygwin" wrote:
> With Cygwin version 3.1.2-1, crtl-c DOES NOT kill native apps that are started from the shell, 

I am investigating why this happens.
Please wait a while.

-- 
Takashi Yano <takashi.yano@nifty.ne.jp>

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