X-Recipient: archive-cygwin AT delorie DOT com
X-Spam-Check-By: sourceware.org
From: "Gary R. Van Sickle" <g DOT r DOT vansickle AT worldnet DOT att DOT net>
To: <cygwin AT cygwin DOT com>
References: <478BD708 DOT 9020909 AT gmail DOT com>  <03ae01c8571d$cfd378f0$2e08a8c0 AT CAM DOT ARTIMI DOT COM>  <000001c85724$418dcb70$020aa8c0 AT DFW5RB41> <EQIjHx3lQjMV092yn AT verizon DOT net>
Subject: RE: [1.7.0 HEAD]: Cygwin no longer encoding/decoding names on managed
Date: Tue, 15 Jan 2008 19:14:54 -0600
Message-ID: <001901c857dd$345d0740$020aa8c0@DFW5RB41>
MIME-Version: 1.0
Content-Type: text/plain; 	charset="us-ascii"
Content-Transfer-Encoding: 7bit
X-Mailer: Microsoft Office Outlook 11
In-Reply-To: <EQIjHx3lQjMV092yn@verizon.net>
X-IsSubscribed: yes
Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm
Precedence: bulk
List-Id: <cygwin.cygwin.com>
List-Unsubscribe: <mailto:cygwin-unsubscribe-archive-cygwin=delorie DOT com AT cygwin DOT 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

> From: Jeff
> Sent: Tuesday, January 15, 2008 4:00 AM
> Subject: Re: [1.7.0 HEAD]: Cygwin no longer encoding/decoding 
> names on managed

[snip]

> >Managed mounts?  They're intended to handle names with 
> things like ":" 
> >in them, which will choke Windows no matter what year is in its name.
> 
> Aren't they also intended to support apps that expect and 
> require file names to be POSIXly case-sensitive? Apps that 
> include core files that have the same names except for case? 
> ...which will cause file collisions in Windows, no matter 
> what year is in its name.
> 

Yep, that kind of stuff as well.

> It seems to me that Cygwin /still/ has just as much need to 
> map POSIX file names onto Windows, as Windows still has the 
> need (at least through XP-- I do not know if this is 
> supported in Vista) to map long file names onto DOS 8.3 file 
> names.

Like Corinna said, file handling in the tip is a work in progress.  While I
don't want to speak for anybody, I am unaware of any plans to remove this
functionality, as appears to be your concern.

>  Oh yeah, which reminds me-- cygpath no longer escapes 
> the spaces in Windows long file names when converting them to 
> POSIX paths, making the following kludgy shell script
> necessary:
> 
> #! /bin/bash
> ppath=$(cygpath "$2" | sed 's/ /\\ /g')
> if [ -n $3 ] ; then
>   eval $1 "$ppath" $3
> else
>   eval $1 "$ppath"
> fi
> 
> 
> Jeff
>

$ cygpath -u 'c:\Program Files'
/cygdrive/c/Program Files

$ cygpath -v    
cygpath (cygwin) 1.42.4.1
Path Conversion Utility
Copyright 1998, 1999, 2000, 2001, 2002, 2003, 2004, 2005 Red Hat, Inc.
Compiled on Dec 14 2007

Yep, I can replicate your report.  I'm doubt that it's incorrect behavior
though:

$ find /cygdrive/c/Program\ Files/
/cygdrive/c/Program Files/
[...etc...]

-- 
Gary R. Van Sickle


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