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/
|\ _,,,---,,_ [EMAIL PROTECTED] | [EMAIL PROTECTED]
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/
