Autorename doesn't work as expected when files get moved

Help & Support
1

Let's take a Rename command that moves files, here: move files up one folder level.

Rename FROM * TO ..\* RECURSE AUTORENAME

or, if you prefer a Preset:

<?xml version="1.0" encoding="UTF-8"?>
<rename_preset autorename="yes" case="none" ignoreext="yes" recurse="yes" type="normal" version="12">
    <from>*</from>
    <to>..\*</to>
</rename_preset>

Let's assume we have a simple folder structure:

Folder1
    FileA.txt
Folder2
    FileB.txt

After the Rename it will look like this:

Folder1
Folder2
FileA.txt
FileB.txt

Now let's assume the two files have identical names:

Folder1
    File.txt
Folder2
    File.txt

Then I would expect the AUTORENAME to kick in and rename one file like this:

Folder1
Folder2
File.txt
File (1).txt

However, the Rename just moves one file:

Folder1
Folder2
    File.txt
File.txt

How do I get the Autorename to work as expected?

Tested on 12.9 and 12.9.4

TestAutoRename.orp (197 Bytes)

2

This will probably do the same thing better:

Copy MOVE * TO .. WHENEXISTS=rename
3

That was a demo, not what I wanted to do. I noticed this behavior in other Rename commands as well, e.g. Rename PATTERN=* TO=$.\* RECURSE AUTORENAME. So is this a confirmation of my observation (Autorename doesn't work when files get moved)?

4

I haven't checked that yet. Busy finishing off the 12.10 release at the moment.

5

Just tried again with the new WHENEXISTS, but never got a reaction. Might have something to do with

If the PATTERN and TO arguments are both given, the command will normally apply the rename immediately, without prompting for any further interaction;

although e.g. CASE=extlower and RECURSE will not get ignored.

6

Thanks for the report, this will be fixed in the next beta.