X-Recipient: archive-cygwin AT delorie DOT com
X-SWARE-Spam-Status: No, hits=-1.9 required=5.0 	tests=AWL,BAYES_00,SPF_PASS
X-Spam-Check-By: sourceware.org
Message-ID: <496FABB3.1000703@gmail.com>
Date: Thu, 15 Jan 2009 21:33:39 +0000
From: Andy Koppe <andy DOT koppe AT gmail DOT com>
User-Agent: Thunderbird 2.0.0.18 (Windows/20081105)
MIME-Version: 1.0
To: cygwin AT cygwin DOT com
Subject: Re: Another rvxt vs. minTTY 0.3.4
References: <496EDD78 DOT 5070409 AT columbus DOT rr DOT com>
In-Reply-To: <496EDD78.5070409@columbus.rr.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-IsSubscribed: yes
Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm
List-Id: <cygwin.cygwin.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

Paul McFerrin wrote:
> I have another difference between 0.3.4 and 0.3.3 of minTTY and rxvt.
> 
> If you have a long-running script running, any attemps to stop it with 
> either Control-C or Control-\ does nothing.

It's working here. Just tried it with a 'configure' script.

> Seems that minTTY is 
> starting the child process with SIGINT signals disabled.

Signals are left untouched on the way to the child command's exec() 
call, which means the child process will inherit MinTTY's set of ignored 
signals. How are you invoking MinTTY?

Would people like to see this behaviour changed so that all child 
process signal handlers are reset to SIG_DFL?

> At the prompt, Control-C is recognized.

I think that's because bash disables pty signal generation and processes 
control characters directly.

Andy



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