starred/pathcopycopy

Fork 0

mirror of https://github.com/clechasseur/pathcopycopy.git synced 2026-04-25 12:15:58 +03:00

[GH-ISSUE #118] [BUG] Follow symlink does not work for directory content #117

New issue

Closed

opened 2026-02-25 21:32:40 +03:00 by kerem · 5 comments

kerem commented

2026-02-25 21:32:40 +03:00

Owner

Originally created by @jackhab on GitHub (May 3, 2020).
Original GitHub issue: https://github.com/clechasseur/pathcopycopy/issues/118

Originally assigned to: @clechasseur on GitHub.

Describe the bug
When network location is accessed via symbolic link its path is not expanded as in the case when the same location is accessed via network drive.

To Reproduce
Map a network location via symbolic link in command line:
mklink /d LinkedPath \\server\some\path
Explorer > right click LinkedPath > Path Copy > Examine the UNC path
Provided UNC path is \%LOCAL-COMPUTER-NAME%\LinkedPath

Expected behavior
Provided UNC path must be \\server\some\path

Software

OS: Windows 10
Path Copy Copy Version 17.0

Originally created by @jackhab on GitHub (May 3, 2020). Original GitHub issue: https://github.com/clechasseur/pathcopycopy/issues/118 Originally assigned to: @clechasseur on GitHub. **Describe the bug** When network location is accessed via symbolic link its path is not expanded as in the case when the same location is accessed via network drive. **To Reproduce** Map a network location via symbolic link in command line: `mklink /d LinkedPath \\server\some\path` Explorer > right click LinkedPath > Path Copy > Examine the UNC path Provided UNC path is \\%LOCAL-COMPUTER-NAME%\LinkedPath **Expected behavior** Provided UNC path must be \\\\server\some\path **Software** - OS: Windows 10 - Path Copy Copy Version 17.0

kerem

2026-02-25 21:32:40 +03:00

closed this issue
added the
bug
label

kerem commented

2026-02-25 21:32:41 +03:00

Author

Owner

@clechasseur commented on GitHub (May 8, 2020):

So I took some time replying to this because I no longer have access to a network environment to test UNC paths, but in retrospect I think this has nothing to do with network paths.

I suggest you update to Path Copy Copy 18.0 and use the new "Follow symlink" custom command element support. Here is an exported command that is based on "Copy Long UNC Path", but with symlink support:

LongUNCPath_symlink.zip

Let me know if it works for you.

@clechasseur commented on GitHub (May 8, 2020): So I took some time replying to this because I no longer have access to a network environment to test UNC paths, but in retrospect I think this has nothing to do with network paths. I suggest you update to [Path Copy Copy 18.0](https://github.com/clechasseur/pathcopycopy/releases/tag/v18.0) and use the new "Follow symlink" custom command element support. Here is an exported command that is based on "Copy Long UNC Path", but with symlink support: [LongUNCPath_symlink.zip](https://github.com/clechasseur/pathcopycopy/files/4596492/LongUNCPath_symlink.zip) Let me know if it works for you.

kerem commented

2026-02-25 21:32:41 +03:00

Author

Owner

@jackhab commented on GitHub (May 11, 2020):

Hi Charles
~~it does not work. I verified in command line (cmd and powershell) the symlink target points to the server path.~~
The custom command works with the symlink directory itself but not for its contents.

@jackhab commented on GitHub (May 11, 2020): Hi Charles ~~it does not work. I verified in command line (cmd and powershell) the symlink target points to the server path.~~ The custom command works with the symlink directory itself but not for its contents.

kerem commented

2026-02-25 21:32:41 +03:00

Author

Owner

@clechasseur commented on GitHub (May 11, 2020):

Interesting twist. 😉
I'll look into it.

@clechasseur commented on GitHub (May 11, 2020): Interesting twist. 😉 I'll look into it.

kerem commented

2026-02-25 21:32:41 +03:00

Author

Owner

@jackhab commented on GitHub (May 11, 2020):

Thanks. I checked it again and I'd like to add that even Windows reports symlink target only for the symlink directory and not for its contents both in cmd dir and Explorer's file properties so it would be super cool to have such feature!

@jackhab commented on GitHub (May 11, 2020): Thanks. I checked it again and I'd like to add that even Windows reports symlink target only for the symlink directory and not for its contents both in cmd dir and Explorer's file properties so it would be super cool to have such feature!

kerem commented

2026-02-25 21:32:41 +03:00

Author

Owner

@clechasseur commented on GitHub (Jun 28, 2020):

This bug has been fixed. From now on, symbolic links that are part of the path (and not just its target) will be correctly followed. This will be available in the next version.

@clechasseur commented on GitHub (Jun 28, 2020): This bug has been fixed. From now on, symbolic links that are part of the path (and not just its target) will be correctly followed. This will be available in the next version.