X-Spam-Check-By: sourceware.org
To: cygwin@cygwin.com
From: Eric Blake <ebb9@byu.net>
Subject:  Re: Bash 3.1.17(8): Scripts on textmode mount get problems with CR characters
Date: Tue, 10 Oct 2006 16:20:10 +0000 (UTC)
Lines: 30
Message-ID:  <loom.20061010T181538-454@post.gmane.org>
References:  <93C4769E3BED6B42B7203BD6F065654C081FDE38@dmoexc01.emea.cpqcorp.net>
Mime-Version:  1.0
Content-Type:  text/plain; charset=us-ascii
Content-Transfer-Encoding:  7bit
User-Agent: Loom/3.14 (http://gmane.org/)
X-IsSubscribed: yes
Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm
List-Subscribe: <mailto:cygwin-subscribe@cygwin.com>
List-Archive: <http://sourceware.org/ml/cygwin/>
List-Post: <mailto:cygwin@cygwin.com>
List-Help: <mailto:cygwin-help@cygwin.com>, <http://sourceware.org/ml/#faqs>
Sender: cygwin-owner@cygwin.com
Mail-Followup-To: cygwin@cygwin.com
Delivered-To: mailing list cygwin@cygwin.com

Bruun, Peter Michael (HP C&I CME OSS CoE <peter-michael.bruun <at> hp.com> 
writes:

> 
> With release 3.1.8 of Bash, however, it no longer understands Windows
> conventions.
> 
> I get:
> 
> Bash is broken in /home/pmb
> Bash is broken in C:/Temp
> Bash works in /tmp
> 
> 
> Or have I overlooked something?

You overlooked bash-3.1-9, which special cases DOS paths to ensure that the 
underlying mount path settings are honored even when you go behind cygwin's 
back by using DOS paths.

You also overlooked several weeks' worth of discussions of this very issue on 
this list, including mail from me stating that I am considering preparing bash-
3.1-10 with the new igncr shopt (possibly turning it into an -o setting, so 
that $SHELLOPTS can affect it) on by default, instead of off by default; as 
igncr is definitely faster for \r\n handling than bash-3.1-6 ever was.

-- 
Eric Blake
volunteer cygwin bash maintainer



--
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/