X-Recipient:	archive-cygwin AT delorie DOT com
X-Spam-Check-By:	sourceware.org
Date:	Fri, 2 Mar 2012 13:46:07 +0100
From:	Corinna Vinschen <corinna-cygwin AT cygwin DOT com>
To:	cygwin AT cygwin DOT com
Subject:	Re: ctrl-c not working during bash command line editing
Message-ID:	<20120302124607.GA5018@calimero.vinschen.de>
Reply-To:	cygwin AT cygwin DOT com
Mail-Followup-To:	cygwin AT cygwin DOT com
References:	<CAD0E44w5y63JWhtJS62Gk1d9pCyksF+DiY3oxRHkH=MPr5VoBQ AT mail DOT gmail DOT com> <CADA_DnPWaHRZUuA-ZBDuup+Rsg+rHbKTjHx24Fji_sy6adRoCQ AT mail DOT gmail DOT com> <20120302101840 DOT GE14404 AT calimero DOT vinschen DOT de> <20120302111027 DOT GA27729 AT calimero DOT vinschen DOT de>
MIME-Version:	1.0
In-Reply-To:	<20120302111027.GA27729@calimero.vinschen.de>
User-Agent:	Mutt/1.5.21 (2010-09-15)
Mailing-List:	contact cygwin-help AT cygwin DOT com; run by ezmlm
List-Id:	<cygwin.cygwin.com>
List-Unsubscribe:	<mailto:cygwin-unsubscribe-archive-cygwin=delorie DOT com AT cygwin DOT 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

On Mar  2 12:10, Corinna Vinschen wrote:
> On Mar  2 11:18, Corinna Vinschen wrote:
> > On Mar  1 19:22, Kitchens wrote:
> > > I've noticed this as well, and it seems to be a difference between
> > > /dev/consX and /dev/ptyX ttys. Mintty seems to work fine, whereas
> > > cmd.exe or Console2 (basically a cmd wrapper) cannot CTRL+C on the
> > > command line to abort it. Ctrl+C does, however, issue a SIGINT for a
> > > running process.
> > 
> > Confirmed.  If you start an interactive subshell, Ctrl-C starts working
> > again in there, so this only affects the parent process in a console.
> > 
> > I think I see where this is coming from.  I applied a patch to CVS which
> > fixes this issue, at least for applications calling tcsetattr, like
> > interactive processes usually do.  AFAICS, there's another patch required
> > for non-interactive processes.
> 
> No, that was based on a wrong assumption, apparently.  All apps I started
> could be stopped w/ Ctrl-C now.

I juct created a developer snapshot for testing.  Please give it a try:
http://cygwin.com/snapshots/


Corinna

-- 
Corinna Vinschen                  Please, send mails regarding Cygwin to
Cygwin Project Co-Leader          cygwin AT cygwin DOT com
Red Hat

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