Re: Ctrl-C for non cygwin programs - terminal hangs for over 30 seconds

2013-07-02 Thread Corinna Vinschen
On Jul 2 12:52, Pawel Jasinski wrote: hi, after upgrading to 1.7.20 (from 1.7.not sure) I have noticed that Ctrl-C in terminal doesn't do what it used to. Steps to reproduce: 1. start non-cygwin program, e.g. kdiff3 or notepad 2. press Ctrl-C in terminal 3. non-cygwin program is not

Re: Ctrl-C and non-Cygwin programs

2012-05-27 Thread Mark Lofdahl
References: 4f73cf37.4020...@elfmimi.jp On 28/03/2012 10:55 PM, Ein Terakawa wrote: What it does actually is it generates CTRL_BREAK_EVENT with Windows Console API GenerateConsoleCtrlEvent on the arrival of SIGINT. And to make this scheme to be functional it is required to specify

Re: [PATCH] Ctrl-C and non-Cygwin programs

2012-05-26 Thread Christopher Faylor
On Fri, May 25, 2012 at 11:43:11AM -0700, Mark Lofdahl wrote: References: 4f73cf37.4020...@elfmimi.jp On 28/03/2012 10:55 PM, Ein Terakawa wrote: What it does actually is it generates CTRL_BREAK_EVENT with Windows Console API GenerateConsoleCtrlEvent on the arrival of SIGINT. And to make this

Re: [PATCH] Ctrl-C and non-Cygwin programs

2012-05-25 Thread Mark Lofdahl
References: 4f73cf37.4020...@elfmimi.jp On 28/03/2012 10:55 PM, Ein Terakawa wrote: What it does actually is it generates CTRL_BREAK_EVENT with Windows Console API GenerateConsoleCtrlEvent on the arrival of SIGINT. And to make this scheme to be functional it is required to specify

Re: [PATCH] Ctrl-C and non-Cygwin programs

2012-04-01 Thread Christopher Faylor
On Thu, Mar 29, 2012 at 11:55:51AM +0900, Ein Terakawa wrote: This is a proof of concept demonstration which makes Ctrl-C behave in a way a lot of people expect concerning non-Cygwin console programs. What it does actually is it generates CTRL_BREAK_EVENT with Windows Console API

[PATCH] Ctrl-C and non-Cygwin programs

2012-03-28 Thread Ein Terakawa
from this list, talking about the same topic. Ordered by its significance under my judge. These should help you understand (or remind) what it is about. Date: Mon, 04 Dec 2006 06:24:41 -0800 Subject: Re: Ctrl-C and non-cygwin programs http://cygwin.com/ml/cygwin/2006-12/msg00151.html Date: Thu

RE: Ctrl-C and non-cygwin programs

2006-12-04 Thread Simon Marlow
Brian Dessent wrote: Simon Marlow wrote: Then run the program, hit Ctrl-C and see what happens. The behaviour differs depending on the environment: * In a Cygwin shell started from cygwin.bat, with the CYGWIN environment variable empty: correct behaviour, Ctrl-C is caught and

Re: Ctrl-C and non-cygwin programs

2006-12-04 Thread Brian Dessent
(There's no need to CC me individually, I set the Reply-To: to the list.) Simon Marlow wrote: Ok, thanks. So the bit I didn't realise was that a process needs to be attached to an actual Windows console in order to get Ctrl-C events. This is a bit of a problem, because it essentially

Ctrl-C and non-cygwin programs

2006-11-30 Thread Simon Marlow
I'm experiencing strange behaviour with Ctrl-C with non-cygwin programs started from Cygwin bash. Take the following program: #include windows.h #include stdio.h static BOOL WINAPI handler(DWORD dwCtrlType) { switch (dwCtrlType) { case CTRL_C_EVENT

Re: Ctrl-C and non-cygwin programs

2006-11-30 Thread Brian Dessent
Simon Marlow wrote: Then run the program, hit Ctrl-C and see what happens. The behaviour differs depending on the environment: * In a Cygwin shell started from cygwin.bat, with the CYGWIN environment variable empty: correct behaviour, Ctrl-C is caught and handled. * In a