Re: SIGINT generated by Control-C, is not delivered in mintty

2015-07-21 Thread Houder
>> You are the expert on mintty now ... I only observed a "pattern": > let's say maintainer... expert on terminal issues maybe, but not on > Windows API and specifics of POSIX process control... Language, language, Henri! Hi Thomas, 1. Re. "You are the expert on mintty now ..." First of all, my

Re: SIGINT generated by Control-C, is not delivered in mintty

2015-07-21 Thread Thomas Wolff
On 21.07.2015 10:45, Houder wrote: The trick is to make mintty NOT interact with a cons. Not sure in what way mintty would "interact" with the console here. Hi Thomas, You are the expert on mintty now ... I only observed a "pattern": let's say maintainer... expert on terminal issues maybe, but

Re: SIGINT generated by Control-C, is not delivered in mintty

2015-07-21 Thread Houder
>> The trick is to make mintty NOT interact with a cons. > Not sure in what way mintty would "interact" with the console here. Hi Thomas, You are the expert on mintty now ... I only observed a "pattern": - when 'ps ax' shows that mintty is "connected" to a 'cons', SIGINT is ignored - when 'ps

Re: SIGINT generated by Control-C, is not delivered in mintty

2015-07-20 Thread Thomas Wolff
Am 20.07.2015 um 15:40 schrieb Houder: Indeed, it does! When starting it from a desktop shortcut, it works, but when started as a background process, it doesn't. Ah, so that is the "Cygwin console" # i.e. execution of the file Cygwin.bat, located in the "Windows Cygwin root". Actually no, thoug

Re: SIGINT generated by Control-C, is not delivered in mintty

2015-07-20 Thread Ronald Fischer
> > But I can see the effect simpler in this way: Just open a DOS Command > > Window, and in the command line type > > > > c:\cygwin64\bin\zsh -c /usr/bin/mintty > > > > and the error can be reproduced. BTW, same effect with bash instead of > > zsh. > > Understood. > > For the moment, invoke

Re: SIGINT generated by Control-C, is not delivered in mintty

2015-07-20 Thread Houder
>> > Indeed, it does! When starting it from a desktop shortcut, it works, but >> > when started as a background process, it doesn't. >> >> Ah, so that is the "Cygwin console" # i.e. execution of the file >> Cygwin.bat, located in the "Windows Cygwin root". > > Actually no, though the difference doe

Re: SIGINT generated by Control-C, is not delivered in mintty

2015-07-20 Thread Ronald Fischer
> > Indeed, it does! When starting it from a desktop shortcut, it works, but > > when started as a background process, it doesn't. > > Ah, so that is the "Cygwin console" # i.e. execution of the file > Cygwin.bat, located in the "Windows Cygwin root". Actually no, though the difference doesn't ma

Re: SIGINT generated by Control-C, is not delivered in mintty

2015-07-20 Thread Houder
> On Fri, Jul 17, 2015, at 21:03, Thomas Wolff wrote: >> Am 14.07.2015 um 09:44 schrieb Ronald Fischer: >> > Using Cygwin 64 on Windows 7: >> > >> > In a bash or zsh running inside mintty, pressing Control-C has no >> > effect. In a bash or zsh running in a Windows Console, it works fine. >> Ronal

Re: SIGINT generated by Control-C, is not delivered in mintty

2015-07-20 Thread Ronald Fischer
On Fri, Jul 17, 2015, at 21:03, Thomas Wolff wrote: > Am 14.07.2015 um 09:44 schrieb Ronald Fischer: > > Using Cygwin 64 on Windows 7: > > > > In a bash or zsh running inside mintty, pressing Control-C has no > > effect. In a bash or zsh running in a Windows Console, it works fine. > Ronald, can y

Re: SIGINT generated by Control-C, is not delivered in mintty -- another attempt

2015-07-19 Thread Houder
My apologies for the noise ... Please, see appendix (for a, hopefully, legible presentation of my previous entry). (my ISP introduced a different system for webmail - and now I am inconvienced) Henri... Sorry to interfere here, Thomas, but I had a hard time with your description ... It seem

Re: SIGINT generated by Control-C, is not delivered in mintty

2015-07-19 Thread Houder
I have a suspicion that the problem he is facing could be the same I described in https://sourceware.org/ml/cygwin/2015-02/msg00122.html where the issue only occurs if mintty is started from the cygwin console. Sorry to interfere here, Thomas, but I had a hard time with your description ...

Re: SIGINT generated by Control-C, is not delivered in mintty

2015-07-18 Thread Thomas Wolff
Am 14.07.2015 um 11:27 schrieb Achim Gratz: Ronald Fischer mm.st> writes: In a bash or zsh running inside mintty, pressing Control-C has no effect. In a bash or zsh running in a Windows Console, it works fine. ... WJFFM. ... I have a suspicion that the problem he is facing could be the same

Re: SIGINT generated by Control-C, is not delivered in mintty

2015-07-15 Thread Thomas Wolff
On 15.07.2015 10:46, Marco Atzeri wrote: On 7/14/2015 9:44 AM, Ronald Fischer wrote: Using Cygwin 64 on Windows 7: In a bash or zsh running inside mintty, pressing Control-C has no effect. In a bash or zsh running in a Windows Console, it works fine. This can be verified in two ways: (1) Usi

Re: SIGINT generated by Control-C, is not delivered in mintty

2015-07-15 Thread Marco Atzeri
On 7/14/2015 9:44 AM, Ronald Fischer wrote: Using Cygwin 64 on Windows 7: In a bash or zsh running inside mintty, pressing Control-C has no effect. In a bash or zsh running in a Windows Console, it works fine. This can be verified in two ways: (1) Using 'trap': In the shell, we do a trap

Re: SIGINT generated by Control-C, is not delivered in mintty

2015-07-15 Thread Ronald Fischer
On Tue, Jul 14, 2015, at 11:27, Achim Gratz wrote: > Ronald Fischer mm.st> writes: > > Using Cygwin 64 on Windows 7: > > > > In a bash or zsh running inside mintty, pressing Control-C has no > > effect. In a bash or zsh running in a Windows Console, it works fine. > > > > This can be verified i

Re: SIGINT generated by Control-C, is not delivered in mintty

2015-07-14 Thread Achim Gratz
Ronald Fischer mm.st> writes: > Using Cygwin 64 on Windows 7: > > In a bash or zsh running inside mintty, pressing Control-C has no > effect. In a bash or zsh running in a Windows Console, it works fine. > > This can be verified in two ways: > > (1) Using 'trap': > > In the shell, we do a >