X-Recipient: archive-cygwin AT delorie DOT com X-SWARE-Spam-Status: No, hits=1.7 required=5.0 tests=AWL,BAYES_05,DKIM_SIGNED,DKIM_VALID,DKIM_VALID_AU,FREEMAIL_FROM,KHOP_RCVD_TRUST,RCVD_IN_DNSWL_LOW,RCVD_IN_HOSTKARMA_YE X-Spam-Check-By: sourceware.org From: "Mark Lofdahl" To: Subject: Re: Ctrl-C and non-Cygwin programs Date: Sun, 27 May 2012 12:18:49 -0700 Message-ID: <4fc27e1c.e6c8440a.4ec3.ffff97ed@mx.google.com> MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm List-Id: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner AT cygwin DOT com Mail-Followup-To: cygwin AT cygwin DOT com Delivered-To: mailing list cygwin AT cygwin DOT com References: <4F73CF37 DOT 4020001 AT elfmimi DOT 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_NEW_PROCESS_GROUP when creating new non-Cygwin processes. Is there any way for me to get the old behavior? I rely heavily on the ability to press ctrl-c in my non-cygwin console app and have that app receive a CTRL_C_EVENT instead of a CTRL_BREAK_EVENT. Everything worked fine for me before this patch. >To my surprise there seem to be no way to generate CTRL_C_EVENT using API. It is possible to generate a CTRL_C_EVENT, if you pass 0 as the process group id, in which case the event is passed to all process that share the console. Don't know if that would work in this situation. http://msdn.microsoft.com/en-us/library/windows/desktop/ms683155.aspx Thanks, Mark Lofdahl -- 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