Page 1 of 1

Incontinent treatment of full names by the Multi Rename tool [NO BUG]

Posted: 15.04.2026, 09:30
by Forez
There is this peculiar mismatch in treatment of full names


The name of item will succumb to replacement when user enters proper data in

Multi rename > Settings > Search and replace > Search for

and

Multi rename > Settings > Search and replace > Replace with

fields even if the field of

Multi rename > Settings > Pattern > File name

has the default

Code: Select all

[n]
in it


But extension of a file will not be affected if the field of

Multi rename > Settings > Pattern > File extension

has the default

Code: Select all

[e]
in it


At first I thought this was a bug related to closing parenthesis of all kinds, thus created these examples


But you can literally test-out them i.e. try to remove the

Code: Select all

test3
from them or anything that is placed in them after the dot sign using the Replace with field - and you will see that you will fail


Therefore I think this is at least a wrong concept if not a plain bug. Because why does the

Code: Select all

[n]
is ignored / adjustable while the

Code: Select all

[e]
gets to be obeyed / unchangeable, if both of them are the default values that use original strings as basis for renewed data?



I am using Build 946 64-bit Donor Portable & Build 941 32-bit Public Installed

Re: Incontinent treatment of full names by the Multi Rename tool

Posted: 16.04.2026, 15:25
by Marek
I see no problem:
screen_2026-04-16 15-22-44.png

Re: Incontinent treatment of full names by the Multi Rename tool

Posted: 16.04.2026, 16:15
by Forez
I simply forgot to turn off the

Multi rename > Settings > Search and replace > Exclude extension

option


Me molto stupido