X-Spam-Check-By: sourceware.org
Message-ID: <43E0360F.C2CF85F9@dessent.net>
Date: Tue, 31 Jan 2006 20:16:15 -0800
From: Brian Dessent <brian@dessent.net>
MIME-Version: 1.0
To: cygwin@cygwin.com
Subject: Re: cygwin.bat improvements (was Re: Cygwin on XP disapearing terminal     mystery)
References: <013120061516.12540.43DF7F67000B576B000030FC22058891160A050E040D0C079D0A@comcast.net> <87mzhbkb9k.fsf@newsguy.com> <43E02D37.6456298F@dessent.net> <20060201035104.GA12232@trixie.casa.cgf.cx>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
X-IsSubscribed: yes
Reply-To: cygwin@cygwin.com
Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm
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

Christopher Faylor wrote:

> Couldn't it just replace the bash line with:
> 
>   if exist bash.exe goto ok
>   echo **** bash.exe is missing - please install it
>   pause
>   :ok
>   bash --login -i

Well that would certainly work for the case of a missing bash.  I guess
I was thinking that the marker file method would work for a wider range
of brokenness where for whatever reason the shell fails to start and/or
complete its initialization.  Having never experienced this personally I
can't really come up with a set of possible scenarios of brokenness, but
it seems we get do get a lot of "bash window flashes briefly and then
disappears" reports.  Are they all just missing bash.exe?

Brian

--
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple
Problem reports:       http://cygwin.com/problems.html
Documentation:         http://cygwin.com/docs.html
FAQ:                   http://cygwin.com/faq/