Mailing-List: contact cygwin-help@sourceware.cygnus.com; run by ezmlm List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner@sources.redhat.com Delivered-To: mailing list cygwin@sources.redhat.com Date: Thu, 17 May 2001 03:05:25 -0400 From: Christopher Faylor To: cygwin@cygwin.com Subject: Re: gzip 1.3.1 messy output Message-ID: <20010517030525.C17843@redhat.com> Reply-To: cygwin@cygwin.com Mail-Followup-To: cygwin@cygwin.com References: <200105170605.f4H65Cu30561@mailgate3.cinetic.de> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.3.11i In-Reply-To: <200105170605.f4H65Cu30561@mailgate3.cinetic.de>; from automatthias@web.de on Thu, May 17, 2001 at 08:05:12AM +0200 On Thu, May 17, 2001 at 08:05:12AM +0200, Matthias Kring wrote: >Thanks to Gerrit P. Haase! > >I did not set CYGWIN= ...tty... >(but strange anyway, because the new gzip 1.3.1 is the first program >that seems to produce ugly output w/o this setting) gzip sets its stdout to binmode by default. This results in the output that you're seeing. Btw, it's not "gzip 1.3.1". The Cygwin version is 1.3.1. Gzip has its own version. cgf -- Want to unsubscribe from this list? Check out: http://cygwin.com/ml/#unsubscribe-simple