X-Recipient: archive-cygwin@delorie.com
X-SWARE-Spam-Status: No, hits=-2.2 required=5.0 	tests=AWL,BAYES_00,SPF_PASS
X-Spam-Check-By: sourceware.org
From: "David Karr" <dkarr@real.com>
To: ebb9@byu.net, cygwin@cygwin.com
References:  <41FCBA4373FF4228897280824F4627CF@corp.real.com> <4A3FDACE.3060402@cornell.edu> <FB3A080CD486460B81572A5449F34297@corp.real.com> <4A3FE157.9080901@cornell.edu> <79EE5DFDC3DC45F2821CD2441A8A63C5@corp.real.com> <7F307F6AD3334E008D35103D37D60A73@corp.real.com>  <loom.20090623T160132-253@post.gmane.org>
Subject: RE: How to avoid having shell scripts which fail from killing Emacs   shell?
Date: Wed, 24 Jun 2009 10:19:37 -0700
Message-ID: <EAC6E3C03A224B37A3FDF62A0FC8ED97@corp.real.com>
MIME-Version: 1.0
Content-Type: text/plain; 	charset="us-ascii"
Content-Transfer-Encoding: 7bit
In-Reply-To:  <loom.20090623T160132-253@post.gmane.org>
X-IsSubscribed: yes
Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm
Precedence: bulk
List-Id: <cygwin.cygwin.com>
List-Unsubscribe: <mailto:cygwin-unsubscribe-archive-cygwin=delorie.com@cygwin.com>
List-Subscribe: <mailto:cygwin-subscribe@cygwin.com>
List-Archive: <http://sourceware.org/ml/cygwin/>
List-Post: <mailto:cygwin@cygwin.com>
List-Help: <mailto:cygwin-help@cygwin.com>, <http://sourceware.org/ml/#faqs>
Sender: cygwin-owner@cygwin.com
Mail-Followup-To: cygwin@cygwin.com
Delivered-To: mailing list cygwin@cygwin.com

> -----Original Message-----
> From: cygwin-owner@cygwin.com [mailto:cygwin-owner@cygwin.com] On Behalf
> Of Eric Blake
> Sent: Tuesday, June 23, 2009 9:04 AM
> To: cygwin@cygwin.com
> Subject: Re: How to avoid having shell scripts which fail from killing
> Emacs shell?
> 
> David Karr <dkarr <at> real.com> writes:
> 
> > > > > I'm not sure how complicated it needs to be.  My test case gathers
> a
> > > > couple
> > > > > of parameters and then calls a Java (JDK 1.6.0_14) class.
> > >
> > > I found that the key is whether the Java class reads from stdin or
> not.
> >
> > I just tried changing my script to instead just do a "read" with a
> prompt.
> > This does not kill the shell at the end of the script.  When I do it in
> > Java, it kills the shell at the end of the script.  Weird.
> 
> Hmm.  JDK is a native windows app, not a cygwin app.  So maybe the key
> here is
> not just reading stdin, but passing stdin to a non-cygwin app.

That seems reasonable.  In the past, I believe I've seen references to
issues related to I/O interactions with non-cygwin apps.  Does that notion
give any one else a clue to why this might be happening, or how to mitigate
it?


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