Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner AT cygwin DOT com Mail-Followup-To: cygwin AT cygwin DOT com Delivered-To: mailing list cygwin AT cygwin DOT com Date: Wed, 4 Aug 2004 15:34:13 -0400 From: Christopher Faylor To: cygwin AT cygwin DOT com Subject: Re: Interrupts, bash and .cmd scripts Message-ID: <20040804193413.GB21983@trixie.casa.cgf.cx> Reply-To: cygwin AT cygwin DOT com Mail-Followup-To: cygwin AT cygwin DOT com References: <200408041618 DOT i74GIiv21935 AT bug DOT gfm DOT net> <6 DOT 1 DOT 0 DOT 6 DOT 0 DOT 20040804143738 DOT 03719ae0 AT pop DOT prospeed DOT net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <6.1.0.6.0.20040804143738.03719ae0@pop.prospeed.net> User-Agent: Mutt/1.4.1i On Wed, Aug 04, 2004 at 02:44:33PM -0400, Larry Hall wrote: >Pure Win32 programs don't play well with signals generally. And often Win32 programs don't play well with ptys, either. That's undoubtedly what's happening here. So, it's a PTC situation. cgf -- 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/