Re: make, bash, or cygwin bug?

[Earnie Boyd <earnie_boyd at yahoo dot com>]

--- Kai Henningsen <kai@cats.ms> wrote:
> On 8 Oct 99, at 13:41, Earnie Boyd wrote:
-8<-
> > Or, try SET CYGWIN=... nobinmode ... before starting bash.  The [no]binmode
> > switch controls the processing of the pipe and redirect fd's.  If you
> modify
> > this value after you start bash you effect the change only on pipes not
> redirects.
> 
> 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
> problems.)

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:earnie_boyd@yahoo.com>

Newbies, please visit
<http://www.freeyellow.com/members5/gw32/index.html>

(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 cygwin-unsubscribe@sourceware.cygnus.com