Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm
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
Message-ID: <42899626.5040009@pobox.com>
Date: Mon, 16 May 2005 23:58:46 -0700
From: David Arnstein <arnstein AT pobox DOT com>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.7.8) Gecko/20050511
MIME-Version: 1.0
To: cygwin AT cygwin DOT com
Subject: Control-C now propagates to child processes
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit

Here is a behavior that I believe began with the cygwin updates of 
2005-05-16.

I launch a cygwin command window running the bash shell.  From there, I 
run "startxwin.sh."  Yes, this is a X11 launcher, but please bear with 
me.  I think this is a core cygwin issue, not a cygwin/X11 issue.

As a result of executing startwin.sh, an xterm window appears.  It also 
runs the bash shell.  Now I have two windows showing: the original 
cygwin command window, and an xterm window.

If I type control-c into the original cygwin command window, then the 
xterm window gets the interrupt, along with the original cygwin command 
window.  Programs running in both windows get terminated.

I looked into startxwin.sh. The way this shell launches xterm is
	xterm -e /usr/bin/bash -l &

--
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple
Problem reports:       http://cygwin.com/problems.html
Documentation:         http://cygwin.com/docs.html
FAQ:                   http://cygwin.com/faq/