When moving a junction however, TC does recursively delete its contents.
This only applies when moving to another drive, because moving on the same drive will be done similar to a rename.
To reproduce (at least two NTFS drive letters needed to store the junction, e.g. C: and D: ):
- - create a directory C:\TEMP1\TEMP2\TEMP3
- create a junction to C:\TEMP1\TEMP2, stored as C:\TEMP2 (or on another drive)
- move the junction C:\TEMP2 to D:\ (resulting in D:\TEMP2)
Expected result: moving the junction C:\TEMP2 should not alter the dir C:\TEMP1\TEMP2, but instead only move the junction itself
(that would mean creating the junction at the target and deleting it from the source).
If that's not possible, to prevent data loss: TC should refuse to move, at least warn the user,
that data gets moved from a position other than the one selected.
Implementation should not be that hard, because TC is already able to recognize junctions:
on deleting they are treated correctly (not parsed recursively), while not using Explorer method.