X-Spam-Check-By: sourceware.org
Date: Wed, 1 Feb 2006 12:06:08 -0500 (EST)
From: Igor Peshansky <pechtcha AT cs DOT nyu DOT edu>
Reply-To: cygwin AT cygwin DOT com
To: cygwin AT cygwin DOT com
Subject: Re: cygwin.bat improvements (was Re: Cygwin on XP disapearing terminal  mystery)
In-Reply-To: <20060201163737.GE1648@trixie.casa.cgf.cx>
Message-ID: <Pine.GSO.4.63.0602011147430.9860@access1.cims.nyu.edu>
References: <013120061516 DOT 12540 DOT 43DF7F67000B576B000030FC22058891160A050E040D0C079D0A AT comcast DOT net>  <87mzhbkb9k DOT fsf AT newsguy DOT com> <43E02D37 DOT 6456298F AT dessent DOT net>  <20060201035104 DOT GA12232 AT trixie DOT casa DOT cgf DOT cx> <43E0360F DOT C2CF85F9 AT dessent DOT net>  <20060201163737 DOT GE1648 AT trixie DOT casa DOT cgf DOT cx>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm
Precedence: bulk
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

On Wed, 1 Feb 2006, Christopher Faylor wrote:

> On Tue, Jan 31, 2006 at 08:16:15PM -0800, Brian Dessent wrote:
> >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?
>
> That has always been my impression.  Maybe I'm wrong.
>
> OTOH, would people complain bitterly if we just put a pause at the end
> of cygwin.bat.  That would be a very minimal change.

I would.

> I don't use cygwin.bat so I can't say how aggravating this would be.

Very.  This would mean an extra keystroke for every exited bash shell...
Yuck.

However, most bash invocations should exit with a 0 exit code.  So, why
not simply do something like the test below?

if not errorlevel 1 goto nopause
pause
:nopause

Also, "command not found" sets error code to 127, so the "1" above can be
changed to "127".
	Igor
-- 
				http://cs.nyu.edu/~pechtcha/
      |\      _,,,---,,_	    pechtcha AT cs DOT nyu DOT edu | igor AT watson DOT ibm DOT com
ZZZzz /,`.-'`'    -.  ;-;;,_		Igor Peshansky, Ph.D. (name changed!)
     |,4-  ) )-,_. ,\ (  `'-'		old name: Igor Pechtchanski
    '---''(_/--'  `-'\_) fL	a.k.a JaguaR-R-R-r-r-r-.-.-.  Meow!

"Las! je suis sot... -Mais non, tu ne l'es pas, puisque tu t'en rends compte."
"But no -- you are no fool; you call yourself a fool, there's proof enough in
that!" -- Rostand, "Cyrano de Bergerac"

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