Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner AT cygwin DOT com Delivered-To: mailing list cygwin AT cygwin DOT com Message-ID: <044301c198a8$8f0b61a0$0200a8c0@lifelesswks> From: "Robert Collins" To: References: <037a01c197cf$1d0a4000$0200a8c0 AT lifelesswks> <20020107234555 DOT GA11984 AT redhat DOT com> <03ca01c197d9$8a16c510$0200a8c0 AT lifelesswks> <20020108002140 DOT GA12820 AT redhat DOT com> <03f001c197dd$7a9bec10$0200a8c0 AT lifelesswks> <013201c19812$2125e750$0200a8c0 AT lifelesswks> <20020108161950 DOT GC22944 AT redhat DOT com> <01a401c19892$2f5fa8d0$0200a8c0 AT lifelesswks> <20020109003913 DOT GA28328 AT redhat DOT com> <042a01c198a6$b03bb2a0$0200a8c0 AT lifelesswks> <20020109005523 DOT GA28659 AT redhat DOT com> Subject: Re: bash/cmd CTRL-C problem... Date: Wed, 9 Jan 2002 11:57:04 +1100 MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 6.00.2600.0000 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2600.0000 X-OriginalArrivalTime: 09 Jan 2002 00:57:05.0510 (UTC) FILETIME=[8E75D860:01C198A8] === ----- Original Message ----- From: "Christopher Faylor" > So, I think the easiest fix for the current problem is just to do a > 'signal (SIGINT, SIG_IGN)' prior to calling CreateProcess, restoring > the previous signal handler if the CreateProcess fails. You do realise, that thats what I've done, but via the more efficient way of returning TRUE to the signal. > That doesn't solve the double sending of CTRL-Cs but that's a separate > problem, I think. Yes. -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Bug reporting: http://cygwin.com/bugs.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/