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
Message-Id: <4.3.2.7.2.20020111022918.00b63c68@san-francisco.beasys.com>
X-Sender: andyp AT san-francisco DOT beasys DOT com
X-Mailer: QUALCOMM Windows Eudora Version 4.3.2
Date: Fri, 11 Jan 2002 02:34:39 -0800
To: cygwin AT cygwin DOT com
From: Andy Piper <andyp AT bea DOT com>
Subject: Re: bash/cmd CTRL-C problem...
In-Reply-To: <3C3E059B.2080401@ece.gatech.edu>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed

Chris Faylor wrote:

>There is a snapshot up there now which seems to work ok.
>
>Again, many thanks to Robert Collins for tracking this down.
>
>Although I said I wasn't overly interested in tracking this down
>myself, I was interested in seeing the lessening in email traffic that I
>hope this fix engenders.
>
>I do expect that, when this cygwin DLL is released, there could be a
>reaction from another, previously silent camp who relied on the old
>CTRL-C behavior.  I guess it will be interesting to see if that is the
>case.

Many thanks for looking at this. While the iron is hot - this problem is 
still outstanding and I don't know whether you would expect this to be 
fixed also:

Interactive bash shell starts:
         -> shell script using ash starts:
                 -> java program

^C-ing the script does not have any visible effect (i.e. the java program 
is not killed). As noted previously this problem is resolved if you make 
/bin/sh be bash rather than ash.

Thanks

andy


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