X-Recipient: archive-cygwin AT delorie DOT com
X-SWARE-Spam-Status: No, hits=-1.9 required=5.0	tests=AWL,BAYES_00,RCVD_IN_DNSWL_NONE,RCVD_IN_HOSTKARMA_YE
X-Spam-Check-By: sourceware.org
X-Mail-Handler: Dyn Standard SMTP by Dyn
X-Report-Abuse-To: abuse AT dyndns DOT com (see http://www.dyndns.com/services/sendlabs/outbound_abuse.html for abuse reporting information)
X-MHO-User: U2FsdGVkX18q8IM/RedPTQ+2Sb53EG9F
Date: Fri, 3 Aug 2012 09:53:42 -0400
From: Christopher Faylor <cgf-use-the-mailinglist-please AT cygwin DOT com>
To: cygwin AT cygwin DOT com
Subject: Re: Ctrl+C not working with windows programs in Cygwin 1.7.16
Message-ID: <20120803135342.GA21169@ednor.casa.cgf.cx>
Reply-To: cygwin AT cygwin DOT com
Mail-Followup-To: cygwin AT cygwin DOT com
References: <501AF686 DOT 6020109 AT saic DOT com> <0D835E9B9CD07F40A48423F80D3B5A70015C7C AT USA7109MB022 DOT na DOT xerox DOT net> <501BCAB8 DOT 80401 AT saic DOT com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <501BCAB8.80401@saic.com>
User-Agent: Mutt/1.5.20 (2009-06-14)
Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm
Precedence: bulk
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 Fri, Aug 03, 2012 at 08:57:28AM -0400, Roger K. Wells wrote:
>On 08/03/2012 08:48 AM, Nellis, Kenneth wrote:
>> -----Original Message-----
>> From: Roger K. Wells
>> <snip>
>> Getting a PID & using kill just takes too long.
>> -----END Original Message-----
>>
>> pkill from the procps package might mitigate the pain.
>> --Ken Nellis
>that too is a work around.
>The point here is what is the rationale for changing the way Cygwin bash 
>works after fifteen years?
>It used to behave like bash on any other OS, now it doesn't.

Well, we basically changed it just to piss you off.  It's a little
disappointing that it took you so long to notice.

What other reason could there possibly be?

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