X-Recipient: archive-cygwin AT delorie DOT com
X-SWARE-Spam-Status: No, hits=-0.6 required=5.0	tests=AWL,BAYES_00,DKIM_SIGNED,DKIM_VALID,DKIM_VALID_AU,FREEMAIL_FROM,RCVD_IN_DNSWL_LOW,TW_YG,T_TO_NO_BRKTS_FREEMAIL
X-Spam-Check-By: sourceware.org
From: Barry Kelly <bkelly DOT ie AT gmail DOT com>
To: cygwin AT cygwin DOT com
Subject: Re: cygpath unable to translate the *nix path to an NTFS junction point
Date: Tue, 18 Jan 2011 06:58:16 +0000
Message-ID: <d9daj6d6ksgllm2pjbcpf1krf7ocq6snqh@4ax.com>
References: <AANLkTik5e=pvzaqW+Rxq33NQu1AyaAq3uLmZD3Cb8s5N AT mail DOT gmail DOT com> <1ra7j6h9scktvnlpdceejo3i3q4k4f5c3c AT 4ax DOT com> <20110117135627 DOT GC11221 AT calimero DOT vinschen DOT de> <20110117151142 DOT GE11221 AT calimero DOT vinschen DOT de>
In-Reply-To: <20110117151142.GE11221@calimero.vinschen.de>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: quoted-printable
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

Corinna Vinschen wrote:

> On Jan 17 14:56, Corinna Vinschen wrote:
> > ...we won't take patches which add arbitrary options to the CYGWIN
> > variable which could also be solved in other ways.  In this special
> > case, only the conversion from POSIX to Win32 paths is affected.
> > This conversion is only supported by the cygwin_conv_path function
> > and, subsequently, the cygpath utility.  Therefore, such a change
> > should be restricted to this API.  I'll have a look into adding
> > something along these lines.
>=20
> Try the latest developer snapshot from http://cygwin.com/snapshots/
> It contains a patch which should help in most cases.

It works in many places, but not always.

In particular, the path ".." when the current ($PWD) directory is a
junction is interpreted along the lines as a symlink: to the parent of
the target. I do enough file operations between parent and child, where
the child is a junction, that I'll stick with my own patch.

Another inconsistency in it is shown in this dialog:

~/incoming/dl$ pwd
/home/barrkel/incoming/dl
~/incoming/dl$ cygpath -aw .
M:\mathom\_c_Documents and Settings_barrkel_Downloads
~/incoming/dl$ cygpath -aw $PWD
C:\cygwin\home\barrkel\incoming\dl
~/incoming/dl$ cygpath -aw $PWD/.
M:\mathom\_c_Documents and Settings_barrkel_Downloads
~/incoming/dl$ cygpath -aw $PWD/..
C:\cygwin\home\barrkel\incoming

$PWD/. is at odds with $PWD and $PWD/..

-- Barry

--=20
http://blog.barrkel.com/

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