-
Notifications
You must be signed in to change notification settings - Fork 30.3k
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
Expect to be able to use UI to move relative symbolic links #92731
Comments
Version |
Please update to latest version (1.43) and retest. |
Tried updating but it says I'm on the latest. I'm running on a mac. |
What macOS version? |
10.14.6 |
See #7426 (comment) for advice on how to update. |
Thanks for filling this issue. Can you reproduce using Visual Studio Code Insiders https://code.visualstudio.com/insiders/ |
This issue has been closed automatically because it needs more information and has not had recent activity. See also our issue reporting guidelines. Happy Coding! |
Create a symbolic link
ln -s ../still/in/the/repro/foo.js foo.js
to a file using a relative path such that the link and its target remain in the git repo. Try to use VS Code to move the link from one directory to another.I expect VS code will detect the symbolic link is relative and pointing to a file in the repro and so will "move" the link by deleting the old link and creating a new link with a relative path that points to the same target but from the directory into which I dragged the linked file.
What actually happens is that the link is deleted but no new link is created presumably because VS code doesn't like to display UI for the now broken link (which is a separate bug #44908 which would make sense to fix if this were also fixed).
The text was updated successfully, but these errors were encountered: