This is the mail archive of the
mailing list for the Cygwin project.
Re: SIGINT generated by Control-C, is not delivered in mintty
- From: "Houder" <houder at xs4all dot nl>
- To: cygwin at cygwin dot com, "Ronald Fischer" <ynnor at mm dot st>
- Date: Mon, 20 Jul 2015 15:40:24 +0200
- Subject: Re: SIGINT generated by Control-C, is not delivered in mintty
- Authentication-results: sourceware.org; auth=none
- References: <1436859879 dot 3576693 dot 323109769 dot 13A8B37B at webmail dot messagingengine dot com> <55A9517A dot 5090308 at towo dot net> <1437389942 dot 2804270 dot 328057057 dot 1FF478B2 at webmail dot messagingengine dot com> <6e51c4c1411fb3878b6d7862d96ef4af dot squirrel at oude-webmail dot xs4all dot nl> <1437396634 dot 2825938 dot 328138033 dot 1915DBE0 at webmail dot messagingengine dot com>
>> > 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 matter - but for the safe
> side, here are the gory details:
> In a cmd.exe Command window (or, to be more precise, in a command window
> hosted by the Console2 console), I use the command
> cmd /c c:\cygwin64\bin\zsh -l
> to start an interactive zsh Shell, and from *this*, I start a Ruby
> program, and from *this*, a mintty is started in the background.
> 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
For the moment, invoke mintty through cmd, i.e. put cmd between Ruby and
mintty. That should help.
The trick is to make mintty NOT interact with a cons.
Problem reports: http://cygwin.com/problems.html
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple