X-Recipient: archive-cygwin@delorie.com
X-SWARE-Spam-Status: No, hits=-0.9 required=5.0 	tests=AWL,BAYES_50,SPF_PASS
X-Spam-Check-By: sourceware.org
From: "David Karr" <dkarr@real.com>
To: cygwin@cygwin.com
Subject: How to avoid having shell scripts which fail from killing Emacs shell?
Date: Mon, 22 Jun 2009 07:53:33 -0700
Message-ID: <41FCBA4373FF4228897280824F4627CF@corp.real.com>
MIME-Version: 1.0
Content-Type: text/plain; 	charset="us-ascii"
Content-Transfer-Encoding: 7bit
X-IsSubscribed: yes
Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm
List-Id: <cygwin.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

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 think it's possible to code the scripts to use "trap", which might avoid
this problem, but sometimes (most times, really) I can't change the script.
Is there some way to configure Bash/Cygwin, perhaps in the .emacs_bash
script to mitigate this, without significant tradeoffs?



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