On Jan 17 02:48, Barry Kelly wrote:
Pierce Morton wrote:
I've recently installed cygwin using the web installer, and have found
an error in the way that cygpath translates junction point paths from
*nix to Windows paths when dealing with a junction point.
The issue is that Cygwin
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
Corinna Vinschen wrote:
On Jan 17 02:48, Barry Kelly wrote:
Also, if you don't treat juntions to the same drive as symlinks you have
the problem that you can easily create loops when you run a recursive
file search.
This is true; though 'find' will detect such loops, and e.g. cmd /c dir
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
Corinna Vinschen wrote:
This leaves cygpath completely unable to translate the original path
of an NTFS junction. This is proving to be a problem for me (I'm
trying to use the output of cygpath for the equivalent of a backtick
operation in another script...)
Sorry if I don't get your
Pierce Morton wrote:
I've recently installed cygwin using the web installer, and have found
an error in the way that cygpath translates junction point paths from
*nix to Windows paths when dealing with a junction point.
The issue is that Cygwin treats reparse points as symlinks. IMO, the
more
On Nov 24 14:24, Pierce Morton wrote:
I took a look at the behaviour of cygpath when using cygwin symlinks
and I understand now why it does what it does with junction points.
Consistency between the two seems reasonable if that was its existing
behaviour before junction support was added.
Greetings, Pierce Morton!
However, the real reparse points mounting different volumes...
[C:\]$ uname -a
CYGWIN_NT-5.1 daemon2 1.7.7(0.230/5/3) 2010-08-31 09:58 i686 Cygwin
[C:\]$ dir C:\ | grep arc
2010-11-22 12:16 JUNCTION arc
[C:\]$ cygpath -w /c/arc
C:\arc
Real junction
On Nov 23 12:34, Pierce Morton wrote:
If you've got a junction point (let's call it JUNC, located at
c:\example\junc ) and a real folder TARG (located at c:\example\TARG )
and your junction point points to TARG:
cygpath -w /cygdrive/c/example/junc
will give you
c:\example\TARG
as your
Greetings, Pierce Morton!
I've recently installed cygwin using the web installer, and have found
an error in the way that cygpath translates junction point paths from
*nix to Windows paths when dealing with a junction point.
If you've got a junction point (let's call it JUNC, located at
On Wed, Nov 24, 2010 at 12:09 PM, Andrey Repin anrdae...@freemail.ru wrote:
Greetings, Pierce Morton!
This is expected behavior for cross-links.
I took a look at the behaviour of cygpath when using cygwin symlinks
and I understand now why it does what it does with junction points.
Consistency
I've recently installed cygwin using the web installer, and have found
an error in the way that cygpath translates junction point paths from
*nix to Windows paths when dealing with a junction point.
If you've got a junction point (let's call it JUNC, located at
c:\example\junc ) and a real folder
12 matches
Mail list logo
