X-Recipient: archive-cygwin@delorie.com
X-SWARE-Spam-Status: No, hits=-2.0 required=5.0 	tests=AWL,BAYES_00,SARE_MSGID_LONG40
X-Spam-Check-By: sourceware.org
MIME-Version: 1.0
Date: Mon, 22 Feb 2010 15:42:45 +0000
Message-ID: <416096c61002220742o50cee833paff2efe804e2a400@mail.gmail.com>
Subject: [1.7.2] change in cygpath -w behaviour?
From: Andy Koppe <andy.koppe@gmail.com>
To: cygwin@cygwin.com
Content-Type: text/plain; charset=UTF-8
X-IsSubscribed: yes
Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm
List-Id: <cygwin.cygwin.com>
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

It seems there's been a change in 'cygpath -w' behaviour. Is this intentional?

On 1.7.1 (with C:\ as Cygwin root):
$ cygpath -w /tmp
C:\tmp

On 1.7.2s(0.222/5/3) 20100219 12:56:31:
$ cygpath -w /tmp
\\?\C:\tmp

The latter breaks scripts that aren't sufficiently careful about
backslash quoting, because "\\?\C:\tmp" loses a vital backslash during
quote removal.

Andy

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

