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 Date: Tue, 1 Mar 2005 07:58:53 -0500 From: Christopher Faylor To: cygwin AT cygwin DOT com Subject: Re: cygwin bughunt (snapshot) Message-ID: <20050301125853.GC5876@trixie.casa.cgf.cx> Reply-To: cygwin AT cygwin DOT com References: <79F81D5F4790D344B05F489CE2AC8AB7146D89 AT dubexdc03 DOT dubex DOT net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <79F81D5F4790D344B05F489CE2AC8AB7146D89@dubexdc03.dubex.net> User-Agent: Mutt/1.4.1i On Tue, Mar 01, 2005 at 09:08:04AM +0100, David Dindorp wrote: >Cristopher Faylor wrote: "Christopher" >>Anyway, this sounds a lot like the bash problem which has been >>discussed here over the last several months (most heavily in the >>October time frame). If you aren't running bash-2.05b-17 then >>that's probably your problem. > >bash 3.0 is not good enough? If you are running your own version of bash, then all bets are off. I thought that bash-2.05b-17 was the current version but it is actually a test version designed to handle the problem that you are apparently describing. I'll follow up in cygwin-apps to see why this version is still in test. >I went through the archives for October (anything related to "bash"), >but couldn't find anything that seems related to me. Would you mind >pointing me in the right direction (subject, link, anything)? Sorry, no. I'm not going to do an archive search for you. Maybe someone else will accommodate you. cgf -- 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/