Say that I set up a symbolic link:
mklink /D C:\root\Public\mytextfile.txt C:\root\Public\myothertextfile.txt
Editor's note: Option /D
- which is for creating directory symlinks - is at odds with targeting files, as in this example, which has caused some confusion. To create a file symlink, simply omit /D
.
Is there a way to see what the target of mytextfile.txt
is, using the command line?
Overview. Symlinks, or symbolic links, are “virtual” files or folders which reference a physical file or folder located elsewhere, and are an important feature built in to many operating systems, including Linux and Windows. The Windows' NTFS file system has supported symlinks since Windows Vista.
To check the location of Symlinks and Junction Points in Windows 7 or Windows 10... Via Windows Explorer: Open the parent folder of the suspected symlink or junction point. (Note that symlinks and junction points get a shortcut icon applied in Windows 10 - not sure about Windows 7.)
The Symlink option (Symlink Target Operations) only appears in the context menu from ClearCase Explorer after right-clicking on an actual symbolic link. If the symlink target is in another VOB, then that VOB must also be mounted on the local system.
As Harry Johnston said dir
command shows the target of symbolic links
2014/07/31 11:22 <DIR> libs 2014/08/01 13:53 4,997 mobile.iml 2014/07/31 11:22 689 proguard-rules.pro 2014/09/28 10:54 <JUNCTION> res [\??\C:\Users\_____\mobile\src\main\res]
If you love us? You can donate to us via Paypal or buy me a coffee so we can maintain and grow! Thank you!
Donate Us With