X-Recipient:	archive-cygwin AT delorie DOT com
X-SWARE-Spam-Status:	No, hits=-1.5 required=5.0 tests=AWL,BAYES_00,KHOP_THREADED,T_RP_MATCHES_RCVD
X-Spam-Check-By:	sourceware.org
Message-ID:	<4F8D1867.7000604@tlinx.org>
Date:	Tue, 17 Apr 2012 00:14:47 -0700
From:	Linda Walsh <cygwin AT tlinx DOT org>
User-Agent:	Mozilla/5.0 (Windows; U; Windows NT 6.0; en-US; rv:1.8.1.24) Gecko/20100228 Lightning/0.9 Thunderbird/2.0.0.24 Mnenhy/0.7.6.666
MIME-Version:	1.0
To:	"cygwin AT cygwin DOT com" <cygwin AT cygwin DOT com>
Subject:	Re: 1.7.11: Ctrl-C does not work in bash shell (Win7)
References:	<0105D5C1E0353146B1B222348B0411A20A6536CB73 AT NIHMLBX02 DOT nih DOT gov>
In-Reply-To:	<0105D5C1E0353146B1B222348B0411A20A6536CB73@NIHMLBX02.nih.gov>
X-IsSubscribed:	yes
Mailing-List:	contact cygwin-help AT cygwin DOT com; run by ezmlm
List-Id:	<cygwin.cygwin.com>
List-Subscribe:	<mailto:cygwin-subscribe AT cygwin DOT com>
List-Archive:	<http://sourceware.org/ml/cygwin/>
List-Post:	<mailto:cygwin AT cygwin DOT com>
List-Help:	<mailto:cygwin-help AT cygwin DOT com>, <http://sourceware.org/ml/#faqs>
Sender:	cygwin-owner AT cygwin DOT com
Mail-Followup-To:	cygwin AT cygwin DOT com
Delivered-To:	mailing list cygwin AT cygwin DOT com

Buchbinder, Barry (NIH/NIAID) [E] wrote:

> Spackmann, Richard M. sent the following at Tuesday, April 03, 2012 2:18 PM
>> When I open up a cygwin command line bash shell and I notice now that
>> Ctrl-C does not exit out from the current command prompt to start a new
>> one.
>>
>> Ctrl-C will however exit a running process.
>>
>> Is this to be the behavior from now on, or is a
>> reoccurrence of the possible bug as reported in
>> http://cygwin.com/ml/cygwin/2012-03/msg00102.html.
>>
>> If so, when is the next cygwin bug release due out?
>>
>> I am running Windows 7 and just upgraded to 1.7.11 - attached is the
>> output of cygcheck.
> 
> I think that it may be bash, not cygwin.  Bash does not exit with ^C,
> but will with ^D.
> 
> See SIGNALS in man bash.  (A feature, not a bug.)

----
	It's not that it should exit -- but it used to abort the input
of the current line, and give you a new one --

	I managed to find a combination of stty settings that worked
around it with a side effect of killing any window I press control-C
in if a program is 'stuck'... i'm running bash inside of 'console.exe',
and if I have a program that hangs, pressing control-c kills the prog,
bash and the window -- well -- at least it kills it -- not an idea
change.

I stuck "stty echoctl ignbrk" in my .bashrc, to get the current behavior
which results in bash reverting to it's normal behavior (controlC aborts
current line or kills a shell script waiting for input...), with
the side effect noted above...

Hopefully it will get fixed...


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

- Raw text -