Mailing-List:	contact cygwin-help AT sourceware DOT cygnus DOT com; run by ezmlm
List-Subscribe:	<mailto:cygwin-subscribe AT sources DOT redhat DOT com>
List-Archive:	<http://sources.redhat.com/ml/cygwin/>
List-Post:	<mailto:cygwin AT sources DOT redhat DOT com>
List-Help:	<mailto:cygwin-help AT sources DOT redhat DOT com>, <http://sources.redhat.com/ml/#faqs>
Sender:	cygwin-owner AT sources DOT redhat DOT com
Delivered-To:	mailing list cygwin AT sources DOT redhat DOT com
Date:	Wed, 18 Jul 2001 12:55:53 -0400
From:	Christopher Faylor <cgf AT redhat DOT com>
To:	cygwin AT cygwin DOT com
Subject:	Re: broken CTRL-BREAK handling
Message-ID:	<20010718125553.E15332@redhat.com>
Reply-To:	cygwin AT cygwin DOT com
Mail-Followup-To:	cygwin AT cygwin DOT com
References:	<8F23E55D511AD5119A6800D0B76FDDE1CA2EF5 AT cpex3 DOT channelpoint DOT com>
Mime-Version:	1.0
In-Reply-To:	<8F23E55D511AD5119A6800D0B76FDDE1CA2EF5@cpex3.channelpoint.com>
User-Agent:	Mutt/1.3.19i

On Wed, Jul 18, 2001 at 10:32:35AM -0600, Troy Noble wrote:
>Bottom line... that still feels broken to me if the intent is for
>cygwin (more specifically, the bash shell running with cygwin) to
>be able to launch/stop native win32 apps with the same semantics one
>has come to expect when running cmd shell.
>If that's not the goal, then it's a non-issue.

I don't think that that has ever been a stated goal for cygwin.

What would a program, ported from UNIX expect in this situation?  With
your patch, I believe that it would just unceremoniously terminate with
no way to handle cleanup other than to add windows-specific code for
dealing with ctrl-break.

cgf

--
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple
Bug reporting:         http://cygwin.com/bugs.html
Documentation:         http://cygwin.com/docs.html
FAQ:                   http://cygwin.com/faq/

- Raw text -