0
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:\user\username\deep\path\to\folder\target
rather than
C:\user\username\symlinkname
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).
Roaders
Posted 2019-01-15T13:25:27.583
Reputation: 195
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 – 2019-01-15T13:58:10.380
1I'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 – 2019-01-15T14:04:40.103
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 – 2019-01-16T06:44:08.853
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 – 2019-01-16T20:41:15.547
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 – 2019-01-17T06:41:36.350