X-Recipient:	archive-cygwin AT delorie DOT com
X-SWARE-Spam-Status:	No, hits=-0.5 required=5.0 tests=AWL,BAYES_00,DKIM_SIGNED,DKIM_VALID,DKIM_VALID_AU,FREEMAIL_FROM,RCVD_IN_DNSWL_LOW,TW_YG
X-Spam-Check-By:	sourceware.org
Received-SPF:	pass (google.com: domain of fallofmath AT gmail DOT com designates 10.60.3.72 as permitted sender) client-ip=10.60.3.72;
Authentication-Results:	mr.google.com; spf=pass (google.com: domain of fallofmath AT gmail DOT com designates 10.60.3.72 as permitted sender) smtp.mail=fallofmath AT gmail DOT com; dkim=pass header.i=fallofmath AT gmail DOT com
MIME-Version:	1.0
In-Reply-To:	<CAD0E44w5y63JWhtJS62Gk1d9pCyksF+DiY3oxRHkH=MPr5VoBQ@mail.gmail.com>
References:	<CAD0E44w5y63JWhtJS62Gk1d9pCyksF+DiY3oxRHkH=MPr5VoBQ AT mail DOT gmail DOT com>
Date:	Thu, 1 Mar 2012 19:22:30 -0800
Message-ID:	<CADA_DnPWaHRZUuA-ZBDuup+Rsg+rHbKTjHx24Fji_sy6adRoCQ@mail.gmail.com>
Subject:	Re: ctrl-c not working during bash command line editing
From:	Kitchens <fallofmath AT gmail DOT com>
To:	cygwin AT cygwin DOT com
X-IsSubscribed:	yes
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
X-MIME-Autoconverted:	from quoted-printable to 8bit by delorie.com id q223MpKl028488

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.

This issue has come up a lot in the mailing list archives, but at the
time all solutions pointed to using the "CYGWIN=tty" environment
variable -- which has been removed in the latest updates.

--
-Kitchens
.

On Thu, Mar 1, 2012 at 5:31 PM, Scott McCaskill
<scott DOT mccaskill AT gmail DOT com> wrote:
> I use vi mode (set -o vi) in bash.  A couple of days ago I updated my
> cygwin installation and now I'm no longer able to use ctrl-c to abort
> command line editing.  Specifically, while typing a command or editing
> a previous command from the history, it used to be possible to discard
> the command text and return to a fresh prompt by pressing ctrl-c.  I
> thought it might be something peculiar to my bash configuration, but I
> get the same behavior when running bash with --norc.  I'm fairly
> certain that the last time I updated my cygwin installation prior to
> this was no earlier than December 2011.
>
> Any help is appreciated; let me know if you need more information
> (output of cygcheck -s -v -r attached).
>
> Scott McCaskill
>
> --
> 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

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