On Dec 11 21:25, Brent wrote:
Corinna wrote:
This is not always possible when converting POSIX paths to Win32 paths
for a couple of reasons. One reason is that a relative path might
contain symlinks, another one is that a path containing .. could cross
mount points. To recognize both
On Dec 10 22:34, Brent wrote:
If I execute
mypath=`cygpath -w ../`
echo $mypath
I get
d:\unix\nextVersion\script
OK, d:\unix\nextVersion\script is the correct windows version of the path,
but it is in absolute form. I would prefer it if cygpath left it in relative
form,
On Mon, 10 Dec 2007, Brent wrote:
If I execute
mypath=`cygpath -w ../`
echo $mypath
I get
d:\unix\nextVersion\script
OK, d:\unix\nextVersion\script is the correct windows version of the
path, but it is in absolute form. I would prefer it if cygpath left it
in relative form,
Corinna wrote:
This is not always possible when converting POSIX paths to Win32 paths
for a couple of reasons. One reason is that a relative path might
contain symlinks, another one is that a path containing .. could cross
mount points. To recognize both cases extra processing is necessary
If I execute
mypath=`cygpath -w ../`
echo $mypath
I get
d:\unix\nextVersion\script
OK, d:\unix\nextVersion\script is the correct windows version of the path, but
it is in absolute form. I would prefer it if cygpath left it in relative form,
i.e.
echo $mypath
should output
5 matches
Mail list logo