How to open actual folder that is symlinked (with “real” path) on windows 10
I have setup some symlinks on my system using a script. I actually want to use these symlinks like a shortcut so that when I open the symlink in windows explorer it takes me to the real folder, not the fake folder!
So I want to open
C:userusernamedeeppathtofoldertarget
rather than
C:userusernamesymlinkname
I think that in reality I should be using shortcuts rather than symlinks but they are not as easy to create using a script (especially on my locked down machine at work).
windows windows-10 symbolic-link file-shortcut
add a comment |
I have setup some symlinks on my system using a script. I actually want to use these symlinks like a shortcut so that when I open the symlink in windows explorer it takes me to the real folder, not the fake folder!
So I want to open
C:userusernamedeeppathtofoldertarget
rather than
C:userusernamesymlinkname
I think that in reality I should be using shortcuts rather than symlinks but they are not as easy to create using a script (especially on my locked down machine at work).
windows windows-10 symbolic-link file-shortcut
The behavior you're describing indeed is that of link rather than a symlink. Using the context menu of the Windows Explorer to create them should be easy enough? Why do you need to crate them using a script?
– Seth
Jan 15 at 13:58
1
I've got about 60 to create and the folders are very deeply nested. I also have to rename all the shortcuts after creating them. None of this is hard, just doing it 60 times is time consuming
– Roaders
Jan 15 at 14:04
There are several questions on StackExchange that deal with creating links using batch. That said, maybe you could improve your workflow? Why do you need the original path in the Windows "address" bar? Why is it insufficient to see the symlink path?
– Seth
Jan 16 at 6:44
I get odd behaviour when using the symlink. when running a watch npm job for example the watch does not work, tests do not re-run when a file changes. There were other odd behaviours as well. All the answers about creating shortcuts won't work on my locked down work PC.
– Roaders
Jan 16 at 20:41
Talk to your IT about it? It does sound odd that NPM wouldn't be able to pick them up. On the other hand creating 60 shortcuts to arbitrary directories sounds like you might be able to improve the structure as a whole. If you are able to run NPM it would be odd that you can't run a batch or VBS. It might be that your locked down WS is responsible for NPM showing an odd behavior.
– Seth
Jan 17 at 6:41
add a comment |
I have setup some symlinks on my system using a script. I actually want to use these symlinks like a shortcut so that when I open the symlink in windows explorer it takes me to the real folder, not the fake folder!
So I want to open
C:userusernamedeeppathtofoldertarget
rather than
C:userusernamesymlinkname
I think that in reality I should be using shortcuts rather than symlinks but they are not as easy to create using a script (especially on my locked down machine at work).
windows windows-10 symbolic-link file-shortcut
I have setup some symlinks on my system using a script. I actually want to use these symlinks like a shortcut so that when I open the symlink in windows explorer it takes me to the real folder, not the fake folder!
So I want to open
C:userusernamedeeppathtofoldertarget
rather than
C:userusernamesymlinkname
I think that in reality I should be using shortcuts rather than symlinks but they are not as easy to create using a script (especially on my locked down machine at work).
windows windows-10 symbolic-link file-shortcut
windows windows-10 symbolic-link file-shortcut
asked Jan 15 at 13:25
RoadersRoaders
1401212
1401212
The behavior you're describing indeed is that of link rather than a symlink. Using the context menu of the Windows Explorer to create them should be easy enough? Why do you need to crate them using a script?
– Seth
Jan 15 at 13:58
1
I've got about 60 to create and the folders are very deeply nested. I also have to rename all the shortcuts after creating them. None of this is hard, just doing it 60 times is time consuming
– Roaders
Jan 15 at 14:04
There are several questions on StackExchange that deal with creating links using batch. That said, maybe you could improve your workflow? Why do you need the original path in the Windows "address" bar? Why is it insufficient to see the symlink path?
– Seth
Jan 16 at 6:44
I get odd behaviour when using the symlink. when running a watch npm job for example the watch does not work, tests do not re-run when a file changes. There were other odd behaviours as well. All the answers about creating shortcuts won't work on my locked down work PC.
– Roaders
Jan 16 at 20:41
Talk to your IT about it? It does sound odd that NPM wouldn't be able to pick them up. On the other hand creating 60 shortcuts to arbitrary directories sounds like you might be able to improve the structure as a whole. If you are able to run NPM it would be odd that you can't run a batch or VBS. It might be that your locked down WS is responsible for NPM showing an odd behavior.
– Seth
Jan 17 at 6:41
add a comment |
The behavior you're describing indeed is that of link rather than a symlink. Using the context menu of the Windows Explorer to create them should be easy enough? Why do you need to crate them using a script?
– Seth
Jan 15 at 13:58
1
I've got about 60 to create and the folders are very deeply nested. I also have to rename all the shortcuts after creating them. None of this is hard, just doing it 60 times is time consuming
– Roaders
Jan 15 at 14:04
There are several questions on StackExchange that deal with creating links using batch. That said, maybe you could improve your workflow? Why do you need the original path in the Windows "address" bar? Why is it insufficient to see the symlink path?
– Seth
Jan 16 at 6:44
I get odd behaviour when using the symlink. when running a watch npm job for example the watch does not work, tests do not re-run when a file changes. There were other odd behaviours as well. All the answers about creating shortcuts won't work on my locked down work PC.
– Roaders
Jan 16 at 20:41
Talk to your IT about it? It does sound odd that NPM wouldn't be able to pick them up. On the other hand creating 60 shortcuts to arbitrary directories sounds like you might be able to improve the structure as a whole. If you are able to run NPM it would be odd that you can't run a batch or VBS. It might be that your locked down WS is responsible for NPM showing an odd behavior.
– Seth
Jan 17 at 6:41
The behavior you're describing indeed is that of link rather than a symlink. Using the context menu of the Windows Explorer to create them should be easy enough? Why do you need to crate them using a script?
– Seth
Jan 15 at 13:58
The behavior you're describing indeed is that of link rather than a symlink. Using the context menu of the Windows Explorer to create them should be easy enough? Why do you need to crate them using a script?
– Seth
Jan 15 at 13:58
1
1
I've got about 60 to create and the folders are very deeply nested. I also have to rename all the shortcuts after creating them. None of this is hard, just doing it 60 times is time consuming
– Roaders
Jan 15 at 14:04
I've got about 60 to create and the folders are very deeply nested. I also have to rename all the shortcuts after creating them. None of this is hard, just doing it 60 times is time consuming
– Roaders
Jan 15 at 14:04
There are several questions on StackExchange that deal with creating links using batch. That said, maybe you could improve your workflow? Why do you need the original path in the Windows "address" bar? Why is it insufficient to see the symlink path?
– Seth
Jan 16 at 6:44
There are several questions on StackExchange that deal with creating links using batch. That said, maybe you could improve your workflow? Why do you need the original path in the Windows "address" bar? Why is it insufficient to see the symlink path?
– Seth
Jan 16 at 6:44
I get odd behaviour when using the symlink. when running a watch npm job for example the watch does not work, tests do not re-run when a file changes. There were other odd behaviours as well. All the answers about creating shortcuts won't work on my locked down work PC.
– Roaders
Jan 16 at 20:41
I get odd behaviour when using the symlink. when running a watch npm job for example the watch does not work, tests do not re-run when a file changes. There were other odd behaviours as well. All the answers about creating shortcuts won't work on my locked down work PC.
– Roaders
Jan 16 at 20:41
Talk to your IT about it? It does sound odd that NPM wouldn't be able to pick them up. On the other hand creating 60 shortcuts to arbitrary directories sounds like you might be able to improve the structure as a whole. If you are able to run NPM it would be odd that you can't run a batch or VBS. It might be that your locked down WS is responsible for NPM showing an odd behavior.
– Seth
Jan 17 at 6:41
Talk to your IT about it? It does sound odd that NPM wouldn't be able to pick them up. On the other hand creating 60 shortcuts to arbitrary directories sounds like you might be able to improve the structure as a whole. If you are able to run NPM it would be odd that you can't run a batch or VBS. It might be that your locked down WS is responsible for NPM showing an odd behavior.
– Seth
Jan 17 at 6:41
add a comment |
0
active
oldest
votes
Your Answer
StackExchange.ready(function() {
var channelOptions = {
tags: "".split(" "),
id: "3"
};
initTagRenderer("".split(" "), "".split(" "), channelOptions);
StackExchange.using("externalEditor", function() {
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled) {
StackExchange.using("snippets", function() {
createEditor();
});
}
else {
createEditor();
}
});
function createEditor() {
StackExchange.prepareEditor({
heartbeatType: 'answer',
autoActivateHeartbeat: false,
convertImagesToLinks: true,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: 10,
bindNavPrevention: true,
postfix: "",
imageUploader: {
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
},
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
});
}
});
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fsuperuser.com%2fquestions%2f1394514%2fhow-to-open-actual-folder-that-is-symlinked-with-real-path-on-windows-10%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
0
active
oldest
votes
0
active
oldest
votes
active
oldest
votes
active
oldest
votes
Thanks for contributing an answer to Super User!
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fsuperuser.com%2fquestions%2f1394514%2fhow-to-open-actual-folder-that-is-symlinked-with-real-path-on-windows-10%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
The behavior you're describing indeed is that of link rather than a symlink. Using the context menu of the Windows Explorer to create them should be easy enough? Why do you need to crate them using a script?
– Seth
Jan 15 at 13:58
1
I've got about 60 to create and the folders are very deeply nested. I also have to rename all the shortcuts after creating them. None of this is hard, just doing it 60 times is time consuming
– Roaders
Jan 15 at 14:04
There are several questions on StackExchange that deal with creating links using batch. That said, maybe you could improve your workflow? Why do you need the original path in the Windows "address" bar? Why is it insufficient to see the symlink path?
– Seth
Jan 16 at 6:44
I get odd behaviour when using the symlink. when running a watch npm job for example the watch does not work, tests do not re-run when a file changes. There were other odd behaviours as well. All the answers about creating shortcuts won't work on my locked down work PC.
– Roaders
Jan 16 at 20:41
Talk to your IT about it? It does sound odd that NPM wouldn't be able to pick them up. On the other hand creating 60 shortcuts to arbitrary directories sounds like you might be able to improve the structure as a whole. If you are able to run NPM it would be odd that you can't run a batch or VBS. It might be that your locked down WS is responsible for NPM showing an odd behavior.
– Seth
Jan 17 at 6:41