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 Mail-Followup-To: cygwin AT cygwin DOT com Delivered-To: mailing list cygwin AT cygwin DOT com Reply-To: Cygwin List Message-Id: <6.2.1.2.0.20050801125830.041ccb68@pop.prospeed.net> Date: Mon, 01 Aug 2005 13:01:37 -0400 To: Eric Blake , Mike Chiussi From: Larry Hall Subject: Re: Shell not responding to ctrl+c Cc: cygwin AT cygwin DOT com In-Reply-To: <42EE107B.5070306@byu.net> References: <4efbec0905073120583546c872 AT mail DOT gmail DOT com> <42EE107B DOT 5070306 AT byu DOT net> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" At 08:07 AM 8/1/2005, you wrote: >-----BEGIN PGP SIGNED MESSAGE----- >Hash: SHA1 > >According to Mike Chiussi on 7/31/2005 9:58 PM: >> Recently my harddrive failed and I had to rebuild everything >> (including cygwin, so all old settings are gone) but for some reason >> with this most recent version, the shell (Bash) does not terminate any >> processes when ctrl+c is pressed. > >Are you running in a Windows console? And if so, have you turned on the >CYGWIN=tty setting? As cgf has noted in the past, the tty setting in CYGWIN should not be necessary for proper ctrl+c handling in the Windows console. And indeed I have verified that ctrl+c works for me in the Windows console without setting tty. >Hint - we'd already know that if you attach the cygcheck output, as >requested here: >> Problem reports: http://cygwin.com/problems.html And, as always, this is good advice. :-) -- Larry Hall http://www.rfk.com RFK Partners, Inc. (508) 893-9779 - RFK Office 838 Washington Street (508) 893-9889 - FAX Holliston, MA 01746 -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/