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

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 me

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 >

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