Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm
List-Subscribe: <mailto:cygwin-subscribe AT cygwin DOT com>
List-Archive: <http://sources.redhat.com/ml/cygwin/>
List-Post: <mailto:cygwin AT cygwin DOT com>
List-Help: <mailto:cygwin-help AT cygwin DOT com>, <http://sources.redhat.com/ml/#faqs>
Sender: cygwin-owner AT cygwin DOT com
Delivered-To: mailing list cygwin AT cygwin DOT com
Date: Fri, 4 Jan 2002 12:04:43 -0500
From: Christopher Faylor <cgf AT redhat DOT com>
To: cygwin AT cygwin DOT com
Subject: Re: bash/cmd CTRL-C problem...
Message-ID: <20020104170443.GD30445@redhat.com>
Reply-To: cygwin AT cygwin DOT com
Mail-Followup-To: cygwin AT cygwin DOT com
References: <00f201c18922$2783b180$c51811ac AT brokat DOT de> <003c01c18936$55ca5fd0$c51811ac AT brokat DOT de> <05cb01c18a07$85d72c40$c51811ac AT brokat DOT de> <02f701c19516$5212afa0$c51811ac AT brokat DOT de>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <02f701c19516$5212afa0$c51811ac@brokat.de>
User-Agent: Mutt/1.3.23.1i

On Fri, Jan 04, 2002 at 12:52:43PM +0100, Michael Rumpf wrote:
>I further investigated the bash CTRL-C problem and found out that pressing
>CTRL-C in the bash is "nearly" the same as CTRL-BREAK. I tried all the
>CYGWIN=tty/notty/<empty> combinations but that did not change anything...
>
>[snip]
>
>The cmd shell works as it should be. CTRL-BREAK stops everything immediatly
>and CTRL-C continues with the main thread after the signal was handled.
>
>I guess it is worth mentioning that I don't use any of the Cygwin libc
>stuff. The apps are linked against MS runtime libs.

Here's the harsh reality: it is extremely unlikely that anyone is going
to investigate this.  If you are using non-cygwin apps with bash and
CTRL-C doesn't work then you are on your own.

I will enthusiastically inspect and evaluate any fixes that you provide
to cygwin to rectify this situation.  The fixes must not break current
CTRL-C behavior with cygwin apps.

You are one of a handful of people reporting similar problems.  Everyone
seems to be trying to do basically the same thing.  They're building
non-cygwin java apps and complaining that CTRL-C doesn't work right.

However, since we are all *cygwin* developers it is not likely that
we'll want to go to the effort of loading non-cygwin, java software on
our system to track your problem down for you.  I could be wrong.  Maybe
someone is actively working on this.  If so, I hope that person steps
forward and offers some insight into how they are progressing and what
their proposed fix might be.

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/