You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
ln -s target-file link-name
or
ln -s target-dir link-name
What did you expect to occur after running these commands?
A Windows symbolic link from target file (or target directory) to the link-name specified.
What actually happened instead?
A copy of the target was done to the link-name.
Possible solution:
Suggest at least including winln.exe in Git Bash for Windows (this package is available in msys and can be installed using pacman -Su winln when using Git for Windows SDK. The winln command checks that user has SeCreateSymbolicLinkPrivilege to create symbolic link.
FYI: winln currently does not check if Developer Mode is enabled and will abort creating symlink even though user can create symlinks when this is enabled.
See irakhlin/winln#1
The text was updated successfully, but these errors were encountered:
I think the proper solution might be to expose the MSYS=winsymlinks:nativestrict mode in a more convenient way than having to set that environment variable. Maybe via some sort of /etc/nsswitch.conf knob, or something similar.
Including winln.exe (from wherever) and still having ln -s do the wrong thing, that would probably be the worst thing to do, as it would leave users with the same problem as you faced (unless they learn many details that they should not need to learn).
Setup
Windows 10 Pro 64-bit
defaults?
Using defaults.
to the issue you're seeing?
No.
Details
Bash
Minimal, Complete, and Verifiable example
this will help us understand the issue.
A Windows symbolic link from target file (or target directory) to the link-name specified.
A copy of the target was done to the link-name.
Possible solution:
Suggest at least including
winln.exe
in Git Bash for Windows (this package is available in msys and can be installed usingpacman -Su winln
when using Git for Windows SDK. Thewinln
command checks that user hasSeCreateSymbolicLinkPrivilege
to create symbolic link.FYI:
winln
currently does not check if Developer Mode is enabled and will abort creating symlink even though user can create symlinks when this is enabled.See irakhlin/winln#1
The text was updated successfully, but these errors were encountered: