> -----Original Message----- > From: cygwin-ow...@cygwin.com [mailto:cygwin-ow...@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
