This is the mail archive of the
mailing list for the Cygwin project.
Re: make, bash, or cygwin bug?
- To: Kai Henningsen <kai at cats dot ms>, cygwin at sourceware dot cygnus dot com
- Subject: Re: make, bash, or cygwin bug?
- From: Earnie Boyd <earnie_boyd at yahoo dot com>
- Date: Mon, 11 Oct 1999 05:57:53 -0700 (PDT)
- Reply-To: earnie_boyd at yahoo dot com
--- Kai Henningsen <email@example.com> wrote:
> On 8 Oct 99, at 13:41, Earnie Boyd wrote:
> > Or, try SET CYGWIN=... nobinmode ... before starting bash. The [no]binmode
> > switch controls the processing of the pipe and redirect fd's. If you
> > this value after you start bash you effect the change only on pipes not
> I happen to think this is the wrong type of fix. It's not piping in
> general that should be done in text mode (because there can
> certainly be binary data sent around in pipes - say, the pbm tools),
> but parsing stuff like `` or $(shell ...) (where we _know_ we're
> handling text).
> Typically, these places already have some way to handle '\n' so as
> to make it work as white space. Under cygwin, this should
> probably be extended to '\r'. (This way may well be that later
> parsing routines handle '\n' like white space, not the place that
> takes the output from a program. OTOH, I can see no reason why
> parsing text should ever need to handle '\r' as something different
> from white space, so doing this change should not result in
Sounds interesting. Any chance that you could submit patches? Not having to
worry about \r\n line endings on the read would be great as long as if I wanted
them to be written by default that would still happen.
Earnie Boyd <mailto:firstname.lastname@example.org>
Newbies, please visit
(If you respond to the list, then please don't cc me)
Do You Yahoo!?
Bid and sell for free at http://auctions.yahoo.com
Want to unsubscribe from this list?
Send a message to email@example.com