-
Notifications
You must be signed in to change notification settings - Fork 861
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
symbolic links that work with UNIX and Windows #2995
Comments
OK - now I see this MAYBE fixed in So wondering when that will be released to the general public? |
Next update is called 1803 so if nothing weird happens it should be released next month. |
confirmed! the insider build 17120 is ok |
Using most recent version of ms4w on windows 10 system, I am trying to use symbolic links connect to data on a NAS. They appear to be ignored. The only error message says path is not found. The link was create with mklink /d. When I dir the path / link I see all of the data. |
This bug-tracker is monitored by developers and other technical types. We like detail! So please use this form and tell us, concisely but precisely, what's up. Please fill out ALL THE FIELDS!
If you have a feature request, please post to the UserVoice.
If this is a console issue (a problem with layout, rendering, colors, etc.), please post to the console issue tracker.
Important: When reporting BSODs or security issues, DO NOT attach memory dumps, logs, or traces to Github issues. Instead, send dumps/traces to [email protected], referencing the GitHub bug number. Ideally, please configure your machine to capture minidumps, repro the issue, and send the minidump from "C:\Windows\minidump".
Your Windows build number: (Type
ver
at a Windows Command Prompt)Microsoft Windows [Version 10.0.16299.248]
What you're doing and what's happening: (Copy&paste specific commands and their output, or include screen shots)
in a directory which is mounted drivefs (e.g. /mnt/c/Sandbox/a/b/c)
ln -s ../../Builds
What's wrong / what should be happening instead:
It works FINE in the unix shell
but when I use a windows cmd shell I see
dir
...
03/01/2018 11:02 PM <JUNCTION> Builds [...]
...
and cd Builds produces:
The directory name is invalid.
WSL, cygwin, and mklink all provide windows ways to create symbolic links. And NONE of them work with any of the others. This makes software development still quite painful, and hard to share a code base across different tool sets. In my view - this is the largest remaining impediment to using Windows for UNIX development.
Strace of the failing command, if applicable: (If
some_command
is failing, then runstrace -o some_command.strace -f some_command some_args
, and link the contents ofsome_command.strace
in a gist here)See our contributing instructions for assistance.
The text was updated successfully, but these errors were encountered: