copy symlinks as symlinks

[rjak]

options available?

like:
xcopy /B or
rsync -l, --links

[HolgerK]

options available?

F1, 4b wincmd.ini, CopyLinks

HTH
Holger

[rjak]

thanks for your fast supply!
dont know what F1,4b means. a reference to help?

I set:
[Configuration]
CopyLinks=1 (copy symlinks as symlinks, keep drive letter)

but it effectively uses mode 0 (even as admin)

Details:
Windows 7 64bit
copying SYMLINKD (directory symlinks)

[karlchen]

dont know what F1,4b means. a reference to help?

Exactly. Press F1 to launch the T.C. help. Go to section 4.b which is about parameters in wincmd.ini. Look for the parameter CopyLinks.

CopyLinks=0 Copy file system links (junctions) as links and not as directories:
0: Copy links as dirs or ignore them (if IgnoreLinks has been set)
1: Copy links without changing the target path of the links
2: Copy links and change the target path to the target drive if the link points to the same drive on which the link itself is located.
Example:
c:\path1\link, pointing to c:\path1\path2\linktarget
Copied to d:\trgpath1\trgpath2\link
-> Link now points to d:\trgpath1\trgpath2\path2\linktarget
Note: The function does NOT check whether the target of the link exists or not.

IgnoreLinks=0 Allows to ignore hard links (junctions, reparse points) to directories in various functions. Note: The function "Synchronize dirs" uses a separate option "SyncIgnoreJunctions".
Sum of:
1: copy/move/calculate occupied space
2: internal packers (zip, tar)
4: branch view
8: find files, re-scan tree
16: ignore links even when they are selected in the current directory. Otherwise only links in selected subdirectories are ignored.

[Configuration]
CopyLinks=1 (copy symlinks as symlinks, keep drive letter)

After setting parameters in wincmd.ini manually you may have to restart T.C.

Yet, you should also check for the current value of the parameter IgnoreLinks. In case links are ignored I imagine CopyLinks may not have any real effect.

[rjak]

Thanks. But no, it does not work.

What I tried (in combinations):
IgnoreLinks=0
IgnoreLinks=1
IgnoreLinks=19
restarted tc
verified editing wincmd.ini effects by another value
tried TC7.04a, 7.51a (32bit,64bit)

symlinks, symlinksd are ALWAYS copied as dirs and files.

EVEN IgnoreLinks=1 does not work. so by now I have to use xcopy, rsync for every copy that may contain symlinks

please check this on your own so I might open a bug report

[HolgerK]

tried TC7.04a, 7.51a (32bit,64bit)

CopyLinks is a feature introduced with TC 8.50.
Another reason may be that you are using "Explorer Copy method" or CTRL+C/Ctrl+V to copy files.

Regards
Holger

[Balderstrom]

Another reason might be that you tried to use it on the 4th Sunday in an odd month, without the other option DONT-IGNORELINKS-OR-CHANGE-THEM-JUST-COPY-IT-AS-IS-IT-SHOULDN'T-F'N-MATTER-ABOUT-HALF-A-DOZEN-OTHER-SETTINGS=42.

[HolgerK]

=42.

42 is not the answer (at least in decimal number system).
According to Douglas Adams famous work the question was:
"What do you get if you multiply six by nine?"
So I suggest to try option 54 to get the ultimate solution for this problem.

Regards
Holger

[VSB]

But in 13-based..

[HolgerK]

2VSB

TC supports hexadecimal numbers inside ini files like:

Code: Select all

=$36

but no tridecimal numbers.


Holger

[LeeBinder]

me too!!! PLEASE add the available options..

• into Settings/ Copy options
• into the copy dialog options

THANK YOU CHRISTIAN!

[quantum]

I just tested this again with 9.22a. Regardless of copylinks setting, file symlinks copies the file, not the link. Copying a dir symlink creates a junction which is not the same. I use doublecommander or robocopy if I care about links. Doublecommander works as expected in all cases, although it wants elevation even if I already have rights to create symlinks.

[dindog]

2quantum
the option is only for junction or dir?Anyway I remember the other thread said one will need fastcopy to copy symlink


https://www.ghisler.ch/board/viewtopic.php?f=3&t=50524&p=345097&hilit=symlink+fastcopy#p345097

[ghisler(Author)]

It's only for links to directories, not links to files, they are substantially different.

Links to directories can be distringuished between the actual directory and a link pointing to it.
File system links to files are like separate files which all point to the same data. You cannot distinguish berween the file and link, they are all links.

[umbra]

You cannot tell a difference between the original and newly created hardlinks to a file. But it is easy to detect a symlink to a file. Just like it is easy to detect a symlink to a folder (AKA directory junction, in Microsoft nomenclature).