Total Commander

Posted: **2015-11-17, 18:06 UTC**

MVV wrote:MRT setting dups may be predicted before starting overall rename operation (just like current TC checks for duplicates in resulting names and hints that something may be set wrong)

That's obvious. And this check should stay as it was, IMO.
But I meant duplicates resulting from TC's own rename procedure, where TC can't distinguish in advance that conflicts may arise.
Simple example: having files like
1.txt
2.txt
3.txt
and now trying to rename them in reverse order with [N]
Result: TC tries, but fails of course, due to a lack of "predicting" logic.

Posted: **2015-11-17, 19:11 UTC**

All cases when TC can't predict duplicates are run-time ones IMO. Initial check is just a hint for the user but then conflicts should be resolved by standard auto-rename with appending (2), (3) etc if user allows that.

Result: TC tries, but fails of course, due to a lack of "predicting" logic.

Maybe I don't understand something but I can't reproduce it. What do you mean by reverse order? Even if I reorder files in MRT, TC silently renames files in case of [N] template.

Posted: **2015-11-17, 19:28 UTC**

Sorry, typo.

I meant the [C] field of course.
Either sort files in descending order, mark them and start MRT,
or change order to descending in MRT (name column).

You now have

Code: Select all

old name        new name
3.txt                1.txt
2.txt                2.txt
1.txt                3.txt

-> TC fails to rename

Posted: **2015-11-17, 20:49 UTC**

You're right, TC can't predict dups in such case and begins renaming. I think it may be just another case of run-time dups. It seems that TC only checks for dups within resulting set of names (and it is enough IMO for such hint).

Posted: **2015-11-19, 10:40 UTC**

Another solution would be a two pass approach, like when copying: First do the renaming, and remember which failed (already done). Then ask the user whether he wants to retry these, and append a number in case of duplicates.

Posted: **2015-11-19, 12:19 UTC**

ghisler(Author) wrote:Another solution would be a two pass approach, like when copying: First do the renaming, and remember which failed (already done). Then ask the user whether he wants to retry these, and append a number in case of duplicates.

That's also an possible solution.

---------------------------
Total Commander
---------------------------
Warnung, doppelte Namen! Trotzdem fortfahren?
---------------------------
[Ja] [Nein]
---------------------------

---------------------------
Total Commander
---------------------------
Fehler, konnte die fett dargestellten Dateien nicht umbenennen!
---------------------------
[Add auto suffix] [OK]
---------------------------

---------------------------
Total Commander
---------------------------
Fehler, eine Datei mit diesem Namen existiert bereits in diesem Verzeichnis!
Otto.TXT
---------------------------
[Add auto suffix] [OK]
---------------------------

Posted: **2016-07-07, 14:02 UTC**

08.06.16 Release Total Commander 9.0 beta 1 (32/64)

22.01.16 Added:
Multi-rename tool: If there are duplicate names, or names that already exist,
offer to auto-rename to "name (2).ext", "name (3).ext" etc. (32/64)

Thanks for implementing, First test works fine.

Total Commander

MultiRenameTool: Auto rename on filename collision need

MultiRenameTool: Auto rename on filename collision need