X-Recipient: archive-cygwin AT delorie DOT com X-SWARE-Spam-Status: No, hits=-3.5 required=5.0 tests=AWL,BAYES_00,RCVD_IN_DNSWL_LOW,SPF_HELO_PASS,SPF_PASS X-Spam-Check-By: sourceware.org To: cygwin AT cygwin DOT com From: Eric Blake Subject: Re: How to avoid having shell scripts which fail from killing Emacs shell? Date: Tue, 23 Jun 2009 16:03:50 +0000 (UTC) Lines: 18 Message-ID: References: <41FCBA4373FF4228897280824F4627CF AT corp DOT real DOT com> <4A3FDACE DOT 3060402 AT cornell DOT edu> <4A3FE157 DOT 9080901 AT cornell DOT edu> <79EE5DFDC3DC45F2821CD2441A8A63C5 AT corp DOT real DOT com> <7F307F6AD3334E008D35103D37D60A73 AT corp DOT real DOT com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit User-Agent: Loom/3.14 (http://gmane.org/) X-IsSubscribed: yes Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm List-Id: 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 David Karr 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. -- Eric Blake -- 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