X-Recipient:	archive-cygwin AT delorie DOT com
X-SWARE-Spam-Status:	No, hits=-2.1 required=5.0 tests=AWL,BAYES_00,SPF_PASS
X-Spam-Check-By:	sourceware.org
Message-ID:	<4B172359.70307@tlinx.org>
Date:	Wed, 02 Dec 2009 18:32:57 -0800
From:	Linda Walsh <cygwin AT tlinx DOT org>
User-Agent:	Mozilla/5.0 (Windows; U; Windows NT 6.1; en-US; rv:1.8.1.23) Gecko/20090812 Lightning/0.9 Thunderbird/2.0.0.23 ThunderBrowse/3.2.6.8 Mnenhy/0.7.6.666
MIME-Version:	1.0
To:	"Cygwin List" <cygwin AT cygwin DOT com>
Subject:	Cygwin bug in warning about DOS chars when they are not...
X-Stationery:	0.4.10
X-IsSubscribed:	yes
Mailing-List:	contact cygwin-help AT cygwin DOT com; run by ezmlm
List-Id:	<cygwin.cygwin.com>
List-Subscribe:	<mailto:cygwin-subscribe AT cygwin DOT com>
List-Archive:	<http://sourceware.org/ml/cygwin/>
List-Post:	<mailto:cygwin AT cygwin DOT com>
List-Help:	<mailto:cygwin-help AT cygwin DOT com>, <http://sourceware.org/ml/#faqs>
Sender:	cygwin-owner AT cygwin DOT com
Mail-Followup-To:	cygwin AT cygwin DOT com
Delivered-To:	mailing list cygwin AT cygwin DOT com

I was in bash, and was using shell auto complete to cd to a directory.  
I got to a point where it had placed backslashes in the path to quote dollar
signs and CYGWIN mistakenly threw-up, or threwout an error message about
using DOS PATHS.  I wish it would revert to previous behavior and just 
accept them where used.  Some Windows programs NEED C: in front of them 
to tell THEM what drive THEY are on -- even though cygwin may not care.

Such a change hurts compatibility with windows programs -- which 
any windows user is going to probably use at one point or another while
they are in a bash shell.  I'm *ALWAYS* in a bash shell when use a 
command line in Windows.  I can't stand cmd.exe.

Geez..  But This error is not about my 'side rant' (this error 
message just wound me up...).  This is about Cygwin just being 'wrong' 
about my path...it complained about backslash usage that was being 
used to QUOTE the dollar signs.

Obviously Cygwin is being over-zealous in checking for valid path
specifications in places it shouldn't be checking.

I hit "ESC" (path completion) after I the 0:  ----+
                                                  V
/Users/lin> cd /Windows/Installer/\$PatchCache\$/0cygwin warning:
  MS-DOS style path detected: /Windows/Installer/\$PatchCache\$/
  Preferred POSIX equivalent is: /Windows/Installer//$PatchCache/$/
  CYGWIN environment variable option "nodosfilewarning" turns off this warning.
  Consult the user's guide for more details about POSIX paths:
    http://cygwin.com/cygwin-ug-net/using.html#using-pathnames

---
This resulted in the backslashes being removed and passed to bash, which then
said:

bash: cd: /Windows/Installer/$PatchCache$/0: No such file or directory

Except I hadn't wanted to end the path there...(I easily retyped and fixed
the problem as the error message doesn't happen a 2nd time), but it shouldn't
have happened at all -- I was using "\" as a valid quoting character of "$".

Cygwin ver=1.7.0-67
bash ver=  3.2.49-23
bash-completion ver= 1.1-2



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

- Raw text -