Mailing-List: contact cygwin-help@sourceware.cygnus.com; run by ezmlm
Sender: cygwin-owner@sources.redhat.com
Date: Wed, 27 Sep 2000 12:03:09 -0400
From: Chet Ramey <chet@nike.ins.cwru.edu>
To: cygwin@sources.redhat.com
Subject: Re: Has CR/LF and cat problem with textutils-2.0 been solved?
Cc: chet@po.cwru.edu
Reply-To: chet@po.cwru.edu
Message-ID: <1000927160309.AA92050.SM@nike.ins.cwru.edu>
Read-Receipt-To: chet@po.CWRU.Edu
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii

> >However *all* shells (and not only bash) *must* read the standard
> >output of command expansion (backtick) in *text* mode, as it *does*
> >expect text and is *not* willing to handle binary data there.
> 
> This was my point.  We fixed ash to do the right thing and I've been waiting
> patiently for the bash maintainer to fix bash as well.

How about a bug report?  Or maybe an email?  I don't read this list
very often, so, unless I get mail about it, `waiting patiently' is
probably not going to get the job done.

Now, do you want all '\r's stripped, or \r\n translated to \n when
reading command substitution output?

-- 
``The lyf so short, the craft so long to lerne.'' - Chaucer
( ``Discere est Dolere'' -- chet)

Chet Ramey, CWRU    chet@po.CWRU.Edu    http://cnswww.cns.cwru.edu/~chet/

--
Want to unsubscribe from this list?
Send a message to cygwin-unsubscribe@sourceware.cygnus.com