X-Recipient:	archive-cygwin AT delorie DOT com
X-SWARE-Spam-Status:	No, hits=-0.6 required=5.0 tests=AWL,BAYES_00,RCVD_IN_DNSWL_LOW,SPF_NEUTRAL
X-Spam-Check-By:	sourceware.org
X-Google-DKIM-Signature:	v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20120113; h=mime-version:sender:date:x-google-sender-auth:message-id:subject :from:to:content-type:x-gm-message-state; bh=fV2HloqvzmZJnmFt8r+abOtJAEOvRu4nnxxifDm2K0g=; b=HsG0mzyECEVvqBHymSyEBdGKLCnSD6z9ddvehuMVSQAuYubYnxdGtNynMVgg1Nw+m0 MYXn+rgpk4is5q1dvzLh+rc/mIJR7/dFQeEdilO60aZ2VZq039qs9RD4YGYZpw2v5sIa A2KOpIf+LKq9ATYrDH8TP3BYoju7axglOGszOknSqVVVCe7235Mcx8xbuQZoJhENfvTQ ShgaEpnpOCRoBxlFksGnFmBLVizwFwNrfpUKLe/YmfvUDvVcaKLCsB9XbB3vFp0d7QWm yr/pHQPepWGpmrlo2U82BA6guXTcMdClhGomhKH6lJVqtY3UYNYt5M61WiQm0Q2isM5i 2kCg==
MIME-Version:	1.0
Date:	Fri, 9 Mar 2012 17:09:21 -0800
Message-ID:	<CABT-+2rmK+906QNvfE1Fv5Hzq-UqkxPwArxuARK4xC8f2NXJ=A@mail.gmail.com>
Subject:	bash not responding to control-c when started from cygwin.bat
From:	Pat Tressel <ptressel AT myuw DOT net>
To:	cygwin AT cygwin DOT com
X-Gm-Message-State:	ALoCoQmfV6uyNexmbji+FOep0xIEJUIipMDzFheMic6SjsnUWnPigumPxCiMde7x8Aoc+WUcfr6n
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

Got another console / bash oddity that just started...

When I start a bash window with C:\cygwin\Cygwin.bat, which runs bash as...

bash --login -i

...doing ^C gets no response:  It doesn't clear typing, it doesn't go
back to the shell, it doesn't stop a running program.

If I start bash from another .bat file, but without those options,
there is still no response to ^C.  But if I start bash as a child
process (with no options), ^C works.  That is, steps to reproduce are:

Start Cygwin.bat
$ ^C  <== nothing happens
$ bash
$ ^C  <== normal ^C response
$ exit
$ ^C  <== nothing happens

I'm 98% sure I would have noticed the lack of ^C fairly soon after it
started happening.  Yesterday is when I first noticed it.  Haven't run
setup.exe, didn't change any profile or rc files.  Yeah, I was using
git over in a Windows console, and it's possible it changed something
in the registry entry for HKEY_CURRENT_USER\Console, but I don't see
anything there that seems related to ^C, and Windows console is
responding normally to ^C.  I have a recent backup copy of that branch
in the registry, and it hasn't changed.

Any ideas on what's going on? or what I should check?

Thanks!

-- Pat

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