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: Thu, 12 Feb 2004 10:16:07 -0500 From: Christopher Faylor To: cygwin AT cygwin DOT com Subject: Re: zsh-4.1.1-2 still seems broken under cygwin-1.5.7-1 . Message-ID: <20040212151607.GB997@redhat.com> Mail-Followup-To: cygwin AT cygwin DOT com References: <20040211224830 DOT 18305 DOT qmail AT mti DOT cheetahmail DOT com> <6 DOT 0 DOT 1 DOT 1 DOT 0 DOT 20040212094137 DOT 03921788 AT 127 DOT 0 DOT 0 DOT 1> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <6.0.1.1.0.20040212094137.03921788@127.0.0.1> User-Agent: Mutt/1.4.1i X-IsSubscribed: yes Reply-To: cygwin AT cygwin DOT com On Thu, Feb 12, 2004 at 09:44:26AM -0500, Larry Hall wrote: >As I mentioned before, it's better to verify that the current snapshot does >address the problem you're seeing locally. Otherwise, if you're seeing a >variant or something different than the rest, your problem won't be known >until after 1.5.8 is released. See for the >latest snapshots you can download and try. Right. This is *exactly* why there are problems with zsh. Someone had an easily reproducible problem that showed up in 1.5.6. Rather than report it they apparently waited for 1.5.7 to show up, assuming that all of their problems would be solved. There are still problems with the latest snapshot that I hope to have fixed today. We'll see. 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/