[dolphin] [Bug 504425] New: Better batch (multiple files selected) renaming

Nikoichu bugzilla_noreply at kde.org
Sat May 17 17:31:32 BST 2025


https://bugs.kde.org/show_bug.cgi?id=504425

            Bug ID: 504425
           Summary: Better batch (multiple files selected) renaming
    Classification: Applications
           Product: dolphin
      Version First unspecified
       Reported In:
          Platform: unspecified
                OS: Linux
            Status: REPORTED
          Severity: wishlist
          Priority: NOR
         Component: general
          Assignee: dolphin-bugs-null at kde.org
          Reporter: nikolay_anzarov at abv.bg
                CC: kfm-devel at kde.org
  Target Milestone: ---

When renaming multiple files in Dolphin, you have the option to input "#" for
incremental number. I think it will be a really big improvement if we had
another symbol, for example "%" (or anything else that can't or shouldn't
normally be used in a file name due to compatibility concerns) - and that would
leave the original file name at that spot.

For example, if we have the files:
"icon_16.png" ->                                   -> "icon_16_old.png"
"icon_32.png" -> rename to "%_old" -> "icon_32_old.png"
"icon_ 64.png"                                       -> "icon_64_old.png"

This will be documented below with the text "% will be replaced by each file's
original name."

Additionally, if we provide an extension in the rename, it should replace the
file's current extension:

"icon_16.png" ->                                   -> "icon_16.old"
"icon_32.png" -> rename to "%.old" -> "icon_32.old"
"icon_ 64.png"                                       -> "icon_64.old"

Currently if you rename "icon.png" files to "file#.jpeg", it results in
"file1.jpeg.png", which is probably not what the user intended.

There are probably more possible  improvements to batch renaming, but these are
the most fundamental off the top of my head, and the ones that would be the
most useful to the most people.

-- 
You are receiving this mail because:
You are on the CC list for the bug.


More information about the kfm-devel mailing list