Total Commander

[Balderstrom]

If we have:
C:\Temp\FooLink.txt --> C:\Orig\FooSource.txt

I copy C:\TEMP to D:\BAK, so I now have D:\BAK\TEMP\FooLink.txt
Which points to C:\Orig\FooSource.txt ...

If FooLink.txt is a symlink, then it points to C:\Orig\FooSource.txt
No matter where FooLink.txt is, it still points there.

The fact that it is still a symlink after being copied is to be expected... but if you feel its not expected, TC could notify the user at the end of the Copy Routine that:
There are symlnked files, Replace with Source?

Or something similiar. And/Or have a few checkboxes on the CopyDialog so defaults for handling Junctions/Links can be changed/set. Hide the options by default if so desired. Make the options by default work as TC does now. Then users that don't "get" Links/Junctions will not be bothered by them and will duplicate data like they expect to.

[Đonny]

I think current default behavior of TC when copying Symlinks etc. is OK. It would be however nice to have an option somewhere (in the dialog, special command) to change it.
I'd appreciate if we have option to create symlicks, hardlinks etc. from within Total Commander. E.g. option in F12 dialog - create lnk/symlink or hadrlink. It also would be nice to have option to create symlink with relative path and to change symlink target.
I use Shell Link Extensions to work with symlinks. I also wrote my own utility tor some batch operations (e.g. convert *.lnks to symlink and vice versa).

[schinagl]

:)Some read my (Linkshell Extensions) docu very well. Well if needed for sure I can think of useage of my delorean and smartcopy code in TC. It is all capsuled in a static library, compiles with Vs2005, and does most of the ugly jobs needed to tackle with symlinks/junctions/ whatever

The SmartCopy/Delorean calls can be run async, which means the force a dialog box, to pop up. LSE uses the calls like this. If run sync no progress comes up, and this is the way my ln.exe usese the same functioanlity.

All the usescases from my website come because during development you run into very interesting algorithmic problems.

Or if you would like to write from scratch, also fine I could assist in avoiding run in pitfalls. The only thing I can tell from the experience I gained during the last few years, is that if I knew all those pitfalls in advance I would not have developed it:)

Anyway feel free to contact me:) I am willing to help.

[quote="Balderstrom"]There aren't many more similiar problems.
There are basically two types of junctions/symlinks:
1) Inner Links
2) Outer Links

[mas912]

I have some problem — i *cannot* copy without link contents.
I think, solution of "what user mean" problem, described above, is just a copy option (checkbox): "copy symlink contents" as FAR does.

[JFierce7]

Here's another vote for such a feature:

I've got a backup of a certain PC's drive c, made with FastCopy or TeraCopy.

The backup contains x:\users (as well as x:\documents and settings linked to c:\users), which contains a couple of more junctions ("all users" linked to c:\programdata, "default user" linked to c:\users\default, several "deeper" junctions for appdata a.s.o.).

When I copy this backup from hard disk to hard disk, it doesn't make any sense, to copy the *current* c:\users for "documents and settings". This would be even copied twice, since there's an additional "dokumente und einstellungen". Also it could be possible to ignore "documents and settings" as well as "dokumente und einstellungen", but there are lots of other junctions hidden in the directory structure.

Hence, TC would need some configurable behaviour how to deal with junctions/symlinkd.

Probably all arguments against this proposal as found in postings above, could be raised for moving files as well. However, luckily, TC moves junctions and symlinkd correctly. So why keep this inconsitent behaviour?