X-Recipient:	archive-cygwin AT delorie DOT com
X-SWARE-Spam-Status:	No, hits=-0.6 required=5.0 tests=AWL,BAYES_00,TW_MR,T_RP_MATCHES_RCVD
X-Spam-Check-By:	sourceware.org
Message-ID:	<4F6FCE07.9070407@tlinx.org>
Date:	Sun, 25 Mar 2012 19:01:43 -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:	bug developed in bash in recent release...ignores control-c if typed during input.
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

Normally if I type control-c, it aborts the line I am on, and gives me a new prompt.

After an upgrade a few weeks ago (and retried today with a fresh re-inst of 
bash), the control-c has been getting ignored!

... have to remember line clear... the control-c doesn't echo -- just ignored.

If I look at stty, the setting there says
 > stty
speed 38400 baud; line = 0;
kill = ^X; susp = ^Y;
-imaxbel
-echoe -echok -echoctl -echoke
/Users/law> stty -a
speed 38400 baud; rows 60; columns 80; line = 0;
intr = ^C; quit = ^\; erase = ^?; kill = ^X; eof = ^D; eol = <undef>;
eol2 = <undef>; swtch = ^Z; start = ^Q; stop = ^S; susp = ^Y; rprnt = ^R;
werase = ^W; lnext = ^V; flush = ^O; min = 1; time = 0;
-parenb -parodd cs8 -hupcl -cstopb cread -clocal -crtscts
-ignbrk brkint -ignpar -parmrk -inpck -istrip -inlcr -igncr icrnl ixon -ixoff
-iuclc -ixany -imaxbel
opost -olcuc -ocrnl onlcr -onocr -onlret -ofill -ofdel nl0 cr0 tab0 bs0 vt0 ff0
isig icanon iexten echo -echoe -echok -echonl -noflsh -tostop -echoctl -echoke
---
with relevant parts being the -ignbrk (don't ignore break), intr=^C -- control-c 
still set as interrupt char, though maybe it wasn't on before, but I tried it..
'echoctl'...
(it's on on my linux box)... made no difference...

still ignores controls-c

BUT  -- if I do a stty ignbrk -- then, it works the way it used to.

So is the fact that the settings of 'ignore break' on stty a new feature,
fodder for the 'incident queue', or what?





 > bash --version
bash --version
GNU bash, version 4.1.10(4)-release (i686-pc-cygwin)
Copyright (C) 2009 Free Software Foundation, Inc.
License GPLv3+: GNU GPL version 3 or later <http://gnu.org/licenses/gpl.html>
 > uname -a
uname -a
CYGWIN_NT-6.1-WOW64 Athenae 1.7.11(0.260/5/3) 2012-02-24 14:05 i686 Cygwin

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