X-Recipient:	archive-cygwin AT delorie DOT com
X-SWARE-Spam-Status:	No, hits=-2.1 required=5.0 tests=AWL,BAYES_00,SPF_PASS
X-Spam-Check-By:	sourceware.org
From:	"David Karr" <dkarr AT real DOT com>
To:	kbrown AT cornell DOT edu, cygwin AT cygwin DOT com
References:	<41FCBA4373FF4228897280824F4627CF AT corp DOT real DOT com> <4A3FDACE DOT 3060402 AT cornell DOT edu>
Subject:	RE: How to avoid having shell scripts which fail from killing Emacs shell?
Date:	Mon, 22 Jun 2009 12:38:25 -0700
Message-ID:	<FB3A080CD486460B81572A5449F34297@corp.real.com>
MIME-Version:	1.0
In-Reply-To:	<4A3FDACE.3060402@cornell.edu>
X-IsSubscribed:	yes
Mailing-List:	contact cygwin-help AT cygwin DOT com; run by ezmlm
List-Id:	<cygwin.cygwin.com>
List-Unsubscribe:	<mailto:cygwin-unsubscribe-archive-cygwin=delorie DOT com AT cygwin DOT com>
List-Subscribe:	<mailto:cygwin-subscribe AT cygwin DOT com>
List-Archive:	<http://sourceware.org/ml/cygwin/>
List-Post:	<mailto:cygwin AT cygwin DOT com>
List-Help:	<mailto:cygwin-help AT cygwin DOT com>, <http://sourceware.org/ml/#faqs>
Sender:	cygwin-owner AT cygwin DOT com
Mail-Followup-To:	cygwin AT cygwin DOT com
Delivered-To:	mailing list cygwin AT cygwin DOT com

> -----Original Message-----
> From: cygwin-owner AT cygwin DOT com [mailto:cygwin-owner AT cygwin DOT com] On Behalf
> Of Ken Brown
> Sent: Monday, June 22, 2009 12:26 PM
> To: cygwin AT cygwin DOT com
> Subject: Re: How to avoid having shell scripts which fail from killing
> Emacs shell?
> 
> On 6/22/2009 10:53 AM, David Karr wrote:
> > I've often been annoyed by shell scripts which fail for particular
> > reasons, at which point it causes my Emacs shell buffer to get killed,
> > with "Process shell<2> finished".
> 
> I don't recall ever seeing this happen, but maybe I just don't remember.
>   Can you give me a simple test case?

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.  The class throws
an exception (file not found) in my test case (because I'm deliberately
giving it parameters that will cause that).  If I give it parameters that
will avoid the exception, then it doesn't kill the shell.

Is that enough information to build a test case with?



--
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

- Raw text -