X-Spam-Check-By: sourceware.org Message-ID: <43E0360F.C2CF85F9@dessent.net> Date: Tue, 31 Jan 2006 20:16:15 -0800 From: Brian Dessent MIME-Version: 1.0 To: cygwin AT cygwin DOT com Subject: Re: cygwin.bat improvements (was Re: Cygwin on XP disapearing terminal mystery) 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> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-IsSubscribed: yes Reply-To: cygwin AT cygwin DOT com Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner AT cygwin DOT com Mail-Followup-To: cygwin AT cygwin DOT com Delivered-To: mailing list cygwin AT cygwin DOT 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/