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, 7 Mar 2001 11:19:24 -0500 From: Christopher Faylor To: cygwin@cygwin.com Subject: Re: Broken stdio using sh.exe? Message-ID: <20010307111924.G18117@redhat.com> Reply-To: cygwin@cygwin.com Mail-Followup-To: cygwin@cygwin.com References: <0056890023357703000002L932*@MHS> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.3.11i In-Reply-To: <0056890023357703000002L932*@MHS>; from robert.jan.schutten@philips.com on Wed, Mar 07, 2001 at 01:10:33PM +0100 On Wed, Mar 07, 2001 at 01:10:33PM +0100, robert.jan.schutten@philips.com wrote: >I was under the impression that the reading of text or binary mode of pipes and >non-file devices is controlled by setting CYGWIN to binmode ar nobinmode >(where the default is binmode), see the Cygwin User's Guide: >http://www.cygwin.com/cygwin-ug-net/using-textbinary.html#AEN669 >rule c, which states: >" Pipes and non-file devices are opened in binary mode, except if the CYGWIN > environment variable contains nobinmode." > >If there is the intention to change bash to work like sh works now, then I am in trouble.... >Also this seems to contradict the rule mentions in the Cygwin User's Guide. bash != cygwin sh != cygwin The default for the Cygwin DLL has nothing to do with the decisions that a program like bash or ash may make for its defaults. cgf -- Want to unsubscribe from this list? Check out: http://cygwin.com/ml/#unsubscribe-simple