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: Wed, 29 Nov 2000 15:22:52 -0500 From: Christopher Faylor To: cygwin@cygwin.com Subject: Re: binary mode from non-Cygwin shells? Message-ID: <20001129152252.A17693@redhat.com> Reply-To: cygwin@cygwin.com Mail-Followup-To: cygwin@cygwin.com References: <20001129201228.8576.qmail@web112.yahoomail.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.3.11i In-Reply-To: <20001129201228.8576.qmail@web112.yahoomail.com>; from earnie_boyd@yahoo.com on Wed, Nov 29, 2000 at 12:12:28PM -0800 On Wed, Nov 29, 2000 at 12:12:28PM -0800, Earnie Boyd wrote: >--- Christopher Faylor wrote: >> >> We changed the default some time ago at the request of an, er, customer >> who was distressed at seeing files with \n's and no \r\n's. >> >> Pipes have nothing to do with this. The standard output of a program >> is controlled by the CYGWIN=[no]binmode setting when the program is >> run outside of a cygwin environment. >> >> Undoubtedly the documentation has not been updated to reflect this. >> > >So, if a customer wants it changed to default to binmode, what would he have to >do? ;? Yes sir! I'll change it sir! Especially if the customer is Intel. But, seriously, I actually thought that defaulting to nobinmode when running from a Windows prompt made sense or I wouldn't have changed it. I obviously should have changed the documentation, too. cgf -- Want to unsubscribe from this list? Send a message to cygwin-unsubscribe@sourceware.cygnus.com