MkWhtAdvncdUsrExpctsWhnHWshTCpyC:\n\nToC:\n

[d]

Make what advanced user expects when he wish to copy "C:\n\n" to "C:\n"
i.e.:
warn about replacement, ask for confirmation,
move the file "c:\n\n" to temporary name like "c:\n2",
delete "c:\n",
rename "c:\n2" to "c:\n".

[karlchen]

Hi, d.

Make what advanced user expects when he wish to copy "C:\n\n" to "C:\n"
i.e.:
warn about replacement, ask for confirmation,
move the file "c:\n\n" to temporary name like "c:\n2",
delete "c:\n",
rename "c:\n2" to "c:\n".

This idea/suggestion has been brought up more than once. And it has been rejected as absurd and destructive more than once before. It would break basic rules of the FAT/NTFS filesystems.

Example:

+ Folder "C:\Program Files"
+ File: "C:\Program Files\Program Files"

Your advanced user tells TC to copy "C:\Program Files\Program Files" to "C:\Program Files".

Following your expectation TC will do this:
+ move the file "C:\Program Files\Program Files" to "C:\Program Files2"
+ delete the folder "C:\Program Files".
+ rename the file "C:\Program Files2" to "C:\Program Files"

Congratulations!

The advanced user and his advanced logic have just successfully removed all programmes installed inside the folder "%programfiles%".


My conclusion:

Only fools will expect TC or any filemanager to behave in this way. Advanced users won't.

Regards,
Karl

[roentgen]

2karlchen
That is WAY too bad of an example. Deleting and overwriting are already present in TC and one may destroy important files in many other ways.

BTW if an advanced user moves the file 'Program Files' over the directory 'Program Files' he expects that one is replaced by the other. If he expects something else he's a n00b.

Note: it's not like I'd make any use of such option.

[fenix_productions]

It should be optional with "off" by default.
Why?
- risky
- only these users whom really want this will switch it
- strange behaviour like in example below:
Let's assume you are in "d:\aaaa\" directory and want to move "aaaa" file up on level. What would you do? The best would be F5, write ".." and OK. In the current solution you'd have an error. In proposed solution you should be placed in upper level dir. Let's understand that other files (like "d:\aaaa\xyz.jpg") would be deleted too. For me it could be very strange.

[karlchen]

2karlchen
That is WAY too bad of an example.

No, I disagree. The example is perfectly ok. d's feature request is absurd. (Period)

Karl

[CoMiKe]

Nominated for worst thread title ever...

[roentgen]

2karlchen

d's feature request is absurd. (Period)

I may agree but your example is still bad . You are referring at the possibility to wipe out the 'Program Files' dir with such a feature. This is already possible in TC, you know? (hint: Shift+DEL -- even with less steps).

Anyway... pointless discussion.

[karlchen]

I may agree but your example is still bad . You are referring at the possibility to wipe out the 'Program Files' dir with such a feature. This is already possible in TC, you know? (hint: Shift+DEL -- even with less steps).

Of course, you can. But in this case it is you who deliberately initiates the delete operation.
d requests that TC does this as a side effect of a copy action.

Anyway... pointless discussion.

Agreed, because I trust in Christian's common sense. He will not implement such a feature, not even as an option.

Karl

[d]

there should be an always-appearing confirmation, i.e. even if confirmation disabled, and that should say:
"do you want to delete 12345 files in 123 folders?"

[d]

may be more straight way:
rename c:\n to c:\n2
than
move c:\n2\n to c:\n
than
delete c:\n2.

and when confirmation dialog tc may ask:
"do you want to rename c:\n?"