X-Recipient: archive-cygwin AT delorie DOT com
DomainKey-Signature: a=rsa-sha1; c=nofws; d=sourceware.org; h=list-id
	:list-unsubscribe:list-subscribe:list-archive:list-post
	:list-help:sender:content-type:mime-version:subject:from
	:in-reply-to:date:content-transfer-encoding:message-id
	:references:to; q=dns; s=default; b=N1ko1KdjOiN1KP27pZ5ij8XdUWMV
	9TsvhDXmp1WdmgbpTOrL5itlMDLR0bVwK/NiG+ViDhx63Ejhm4/XNVsfVvhigcud
	MlMUvSSUyUXzq4ATWxLmW96wtUqhG3fdMDLwVKi9IpTxnDJUldRFRN0STGT+Aowl
	8P/2FKObWwyqIRA=
DKIM-Signature: v=1; a=rsa-sha1; c=relaxed; d=sourceware.org; h=list-id
	:list-unsubscribe:list-subscribe:list-archive:list-post
	:list-help:sender:content-type:mime-version:subject:from
	:in-reply-to:date:content-transfer-encoding:message-id
	:references:to; s=default; bh=MCNk/rOX0vZ+NIhoj/Bn4wQm+PI=; b=IA
	K3vy1IGFeWAn9zQTZEbLEtO4tDNQ2VVsoXWzKfv6RssfepLBAj5SFJqUSAsygWVS
	wKJedq7VF3FUYr1b4vbkef+0UlPddD3xY3R/2uKsdgx2aYFMwYOGXkYoOSqVVC7Z
	Z1D/OPwSYIpSykztjnN5f7BpJW/LeJza1gmE3USbI=
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
Authentication-Results: sourceware.org; auth=none
X-Virus-Found: No
X-Spam-SWARE-Status: =?ISO-8859-1?Q?No, score=0.8 required=5.0 tests=AWL,BAYES_40,KAM_LAZY_DOMAIN_SECURITY,RP_MATCHES_RCVD autolearn=no version=3.3.2 spammy=there=e2, productive, H*r:qmail-ldap-1.03, wouldn?=
X-HELO: etr-usa.com
Content-Type: text/plain; charset=utf-8
Mime-Version: 1.0 (Mac OS X Mail 8.2 \(2104\))
Subject: Re: CTRL-C does not work in Cygwin when using pipes
From: Warren Young <wyml AT etr-usa DOT com>
In-Reply-To: <f59f2316e04348b695666247fee14363@ntmaexbe04.bedford.progress.com>
Date: Tue, 29 Dec 2015 16:52:49 -0700
Message-Id: <254A04A5-CF48-4904-9E05-6A6EEFC4B510@etr-usa.com>
References: <f59f2316e04348b695666247fee14363 AT ntmaexbe04 DOT bedford DOT progress DOT com>
To: The Cygwin Mailing List <cygwin AT cygwin DOT com>
X-IsSubscribed: yes
Content-Transfer-Encoding: 8bit
X-MIME-Autoconverted: from quoted-printable to 8bit by delorie.com id tBTNr8on019224

On Dec 29, 2015, at 3:31 PM, Bill Smith <bsmith AT progress DOT com> wrote:
> 
> I'm trying to do this with the standard shell, bash.  We have tried using mintty or the xterm version but there were other issues.

Michael is correct: the shell and the terminal are two separate programs.  Your problem isn’t with bash, it’s with the Windows native console.

If the Windows native console were the best way to run an interactive Cygwin command shell, Cygwin wouldn’t default to mintty these days.

That said, Cygwin *used* to run Bash in the Windows Console by default, and I don’t recall Ctrl-C failing in that case.  So, I guess something changed in the cygwin1.dll terminal I/O handling which breaks Ctrl-C handling while a pipe is running.

While waiting for a fix, maybe a more productive way to solve your problem is to address these “issues” you’re having with mintty.  There’s something to be said for running with the standard environment.
--
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