Mailing-List: contact cygwin-apps-help AT sourceware DOT cygnus DOT com; run by ezmlm list-help: list-post: Sender: cygwin-apps-owner AT sourceware DOT cygnus DOT com Delivered-To: mailing list cygwin-apps AT sourceware DOT cygnus DOT com Date: Thu, 29 Jun 2000 11:20:02 -0400 From: Chris Faylor To: AJ Reins Cc: Corinna Vinschen , cygwin-apps AT sourceware DOT cygnus DOT com Subject: Re: [stephen DOT f DOT tarr AT opbu DOT xerox DOT com: RE: shell back quote expansion problem] Message-ID: <20000629112002.B378@cygnus.com> Mail-Followup-To: AJ Reins , Corinna Vinschen , cygwin-apps AT sourceware References: <20000626160125 DOT A2960 AT cygnus DOT com> <395ACCFA DOT 4D4DB71 AT pop DOT mpls DOT uswest DOT net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2i In-Reply-To: <395ACCFA.4D4DB71@pop.mpls.uswest.net>; from tbisp@uswest.net on Wed, Jun 28, 2000 at 11:13:46PM -0500 On Wed, Jun 28, 2000 at 11:13:46PM -0500, AJ Reins wrote: >Chris Faylor wrote: >> >> Do ash and bash open backquoted pipes in text mode? Should they? >> >> cgf >> > >Bash appears to let the dll handle that, as setting CYGWIN to binmode >or nobinmode does have the appropriate affect. This was the reason >for that particular setting, if memory serves. I can't think of a reason for not setting a back quoted response to text mode, though. When I implemented CYGWIN32=binmode, I was considering the case of the actual pipe '|' character. I thought that it would be nice to make this selectable. I've since come to the conclusion that pipes accessed with '|' should always be binary since it is just too confusing otherwise. I think that `` should also always be text. I can imagine a case where it is vaguely possible that someone would want a \r on their command line but I'd rather have this use suffer than the much more frequent case where the \r is not desired. cgf