-
-
Notifications
You must be signed in to change notification settings - Fork 3.2k
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
[Improved user experience] avoid redundant permission requests #583
Comments
Step 4 is using a junction, which may not work in all environments, but the overall concept of a retry upon failure due to permissions seems like a useful enhancement. It would be nice to reduce/eliminate permission prompts. |
@coreybutler |
@coreybutler |
@Vixb1122 - yes, I know what the junction does, but this can cause problems in some Windows environments, especially those where the junction is made with a directory on another system (NAS/SAN/mapped drive). This is relatively common in corporate environments where the user's home directory is part of a floating Windows profile or is mapped to a different storage system. I've considered making |
Well, your answer is very helpful for me. |
make '/j' an default option is useful to reduce permission prompts. |
any progress on this? |
Because restricted user can execute some command to create symbolic link without permission elevated.
For example: "C:\A_folder"->"C:\B_folder", create symbolic links by the following logic:
cmd /c rmdir "C:\A_folder"
to delete symbolic linkcmd /c mklink /j "C:\A_folder" "C:\B_folder"
to create symbolic linkThe text was updated successfully, but these errors were encountered: