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 Reply-To: Cygwin List Message-Id: <6.1.0.6.0.20040804143738.03719ae0@pop.prospeed.net> X-Sender: Date: Wed, 04 Aug 2004 14:44:33 -0400 To: "Gregory F. March" , Cygwin List From: Larry Hall Subject: Re: Interrupts, bash and .cmd scripts In-Reply-To: <200408041618.i74GIiv21935@bug.gfm.net> References: <200408041618 DOT i74GIiv21935 AT bug DOT gfm DOT net> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" At 12:18 PM 8/4/2004, you wrote: >On Aug 4, 2004, Larry Hall wrote: > |Did you follow the whole thread? I only pointed you to the beginning (so > |you got the context) but it is the later posts that are most relevant to > |your predicament IMO. > >Yes, I did read it. Unless I missed something, the problem is different, and >suggests changing my script - not an option in my case. > >If you read it differently, please point to the specific portion of the >thread so I can see what you are thinking... OK, I was thinking of this one: Pure Win32 programs don't play well with signals generally. If altering your script as described is not an option, you could try adding "notty" to your CYGWIN environment variable (please see the User's Guide for more info). Other than that, I'm outta ideas. -- Larry Hall http://www.rfk.com RFK Partners, Inc. (508) 893-9779 - RFK Office 838 Washington Street (508) 893-9889 - FAX Holliston, MA 01746 -- 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/