From: "David Karr" <dkarr@real.com>
To: kbrown@cornell.edu, cygwin@cygwin.com
References: <41FCBA4373FF4228897280824F4627CF@corp.real.com> <4A3FDACE.3060402@cornell.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
Content-Type: text/plain; 	charset="us-ascii"
Content-Transfer-Encoding: 7bit
In-Reply-To: <4A3FDACE.3060402@cornell.edu>
Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm
Precedence: bulk
Sender: cygwin-owner@cygwin.com
Mail-Followup-To: cygwin@cygwin.com

> -----Original Message-----
> From: cygwin-owner@cygwin.com [mailto:cygwin-owner@cygwin.com] On Behalf
> Of Ken Brown
> Sent: Monday, June 22, 2009 12:26 PM
> To: cygwin@cygwin.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