X-Recipient: archive-cygwin AT delorie DOT 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 AT real DOT com>
To: cygwin AT cygwin DOT 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 AT cygwin DOT com; run by ezmlm
List-Id: <cygwin.cygwin.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

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