Closed ghost closed 7 years ago
Perhaps...
Symlinks and CWD (current working directory) on Windows works differently from Unix. Bash/zsh has the $PWD trick, but still cannot fool getcwd()
. Might be a problem. Another problem is special file names.
http://pubs.opengroup.org/onlinepubs/9699919799/functions/getcwd.html https://msdn.microsoft.com/en-us/library/windows/desktop/aa365247(v=vs.85).aspx#naming_conventions
More notes:
C:file.txt\..
points to C:
(Mind you, not C:\
.), because ..
is resolved before symlinks.C:\..
still points to C:\
, just like the Unix way.\\server\share\..
still points to the prefix \\server\share
.\\.\
is a special prefix for Win32 Device Namespaces.\
for NT Namespaces.File I/O functions in the Windows API convert "/" to "\" as part of converting the name to an NT-style name, except when using the "\\?\" prefix as detailed in the following sections.
This news is very encouraging: https://channel9.msdn.com/Events/Build/2016/C906
_I'm waiting for the next Windows 1y. :stuck_outtongue: