Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain; 	charset="us-ascii"
Subject: RE: Similar Bash 3.1.18 CR/LF Problem
Date: Fri, 29 Sep 2006 11:07:33 -0700
Message-ID: <657A9BE009D3504AAE29BD8E8C2DD61E01A5ABF0@SDGEXEVS02.corp.intuit.net>
In-Reply-To: <451D589C.9070609@cygwin.com>
From: "Wilks, Dan" <Dan_Wilks@intuit.com>
To: <cygwin@cygwin.com>
Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm
Precedence: bulk
Sender: cygwin-owner@cygwin.com
Mail-Followup-To: cygwin@cygwin.com
Content-Transfer-Encoding: 8bit

> >
> > IIRC, Cygwin explicitly treats out-of-mount (Win32) paths as binary.
> > 	Igor
> 
> 
> Yes, that's fits my recollection as well.  Since both of us recall
this,
> there's no need for anyone to check the source.  Two IIRCs means we
must
> be right! ;-)
> 
> 

:) That's how my rulebook works too.  

So we just got the short-end?  A long(?) standing behavior of cygwin
and DOS paths and a recent change to bash that eliminates support for
\r's.  I guess we were living on the edge of something that wasn't 
supposed to work at all and didn't even know it.  :/

We'll try to figure out some workaround for our environment.  I just
wish
going "pure cygwin" was an option.

Thanks for the insights.

--
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple
Problem reports:       http://cygwin.com/problems.html
Documentation:         http://cygwin.com/docs.html
FAQ:                   http://cygwin.com/faq/