It's Suprenam, a batch renaming utility which relies on the tool you know best: your text editor.
Suprenam sits in the Finder Toolbar, waiting for you to drag and drop any selection of files and folders onto it.
Then, it will open your favorite text editor with a list of names. Make use of all your superpowers to modify them: multi-cursors, Find and Replace, regular expressions, you (re)name it.
When you're done, save and close.
The modifications are instantly applied on the selected items.
Suprenam is not as straightforward as it seems. It supports:
-
Complex renamings. As long as the desired final state is possible (e.g. no name clash), Suprenam will abide. Under the hood, this may require it to go through intermediate names (e.g. for swapping
"foo.pdf"and"bar.pdf"). -
Versioning. When an item is tracked by git, Suprenam will use git mvto keep it under version control. -
Rollback. If something goes wrong during the actual process (e.g. a file is moved), don't worry: the work already completed will automatically be rolled back to the initial state.
-
Undo. Likewise, you can always undo the previous renaming session. To that end, simply click the Suprenam icon without dropping anything on it.
-
Download the latest installer from Releases under the name
Suprenam.pkg. It is unsigned: that means that you'll need to right-click or ctrl-click it and select “Open”. -
If you prefer to build it manually, follow these instructions.
-
In both cases, Suprenam requires Python 3.6 or later. You may have to install it.
- Press and hold cmd while dragging the Suprenam icon to the desired location.
No graphical launcher yet. Use the command line tool.
Although dragging and dropping the items to rename them is far more convenient, you can also launch Suprenam from the terminal. Install it with:
pip install suprenam
If this fails, try pip3 instead of pip.
On first launch, Suprenam creates a workspace at:
~/Library/Application Support/Suprenam/(MacOS)~/.config/suprenam/(Linux)%HOMEPATH%\"AppData\Roaming\Suprenam\(Windows)
There, it will put the logs ("log.txt" + some backups) and a configuration file ("config.json") in which you can specify the text editor to use. For instance, VS-Code is the default when the command code is installed in your PATH; if you prefer Sublime Text, just replace the corresponding line by:
- macOS and Linux:
"editor_command": "subl -w",
- Windows
"editor_command": "subl.exe -w",
Many such commands are provided in editor_commands.md, and nothing prevents you from writing your own in the configuration file.
-
Suprenam starts by determining the items to rename. They can be provided:
- directly, as a batch of several files of folders;
- semi-directly, as a single folder: this folder will be renamed, along with all its children (both visible and hidden);
- indirectly, as a single text file (mandatory suffix:
.txt) containing the items to rename (one path by line). Note that a single non-text file will be treated as in the first case.
-
Suprenam retrieves the inodes of the items to be renamed. These unique numeric identifiers will serve as an invariant throughout the renaming process.
-
It creates a temporary TSV file associating each inode with its name. In case all items are siblings (i.e., have the same parent), the list is flat ; otherwise, a group is created for each parent.
-
Note that the list is sorted in “natural order” (e.g., foobar9 before foobar10, and [cote, coteau, crottez, crotté, côte, côté] as [cote, côte, côté, coteau, crotté, crottez]).
-
Suprenam opens this file by invoking the editor command found in the configuration file. If none is specified, it parses
editor_commands.mdand defaults to the first one that happens to work on your system. -
Once the TSV file is opened, Suprenam waits for you to make the desired changes.
-
When it is closed, its content is parsed.
- Any deletion or change to non-inodes lines is ignored.
- The deletion of one, several or even all of the inodes is tolerated.
- However, any inode creation or duplication is considered as a typo, and makes the program to abort without renaming anything.
-
The new names are checked for validity with respect to the actual file system.
-
This results in a list of bindings between existing inodes and modified names. These bindings cannot be directly translated into renaming commands, as they may lead to name clashes.
Below, for instance,
"c"has two “target“ names, which will cause Suprenam to abort…
However, some desired bindings can be resolved along a “safe” path of renamings. For instance, the following renamings (from left to right: null, swapping, shifting, rolling) can always be obtained with careful intermediate renamings.
A handful of accepted and rejected renaming schemes are documented (and tested) here.
-
So, whenever possible, the desired bindings have been silently converted into a “safe” sequence. The new bindings are then processed in order, and the corresponding renaming commands executed. At this stage, the only remaining possible errors should result from hardware failures or from modifications that have occurred in the file tree during the edition stage. Should such rare cases arise, all the completed renaming commands will be readily rolled back.
-
If your fate (or your footgun propensity) is relentless, and this fails too, the program will have no other choice but to leave the file system in a state which is neither the original nor the desired one. You should open the log file at
~/.suprenam/log.txtto see what went wrong and what you can do about it. -
Suprenam can also use this log file to “undo” the previous renaming session by executing the sequence backwards. Obviously, a reversed sequence of safe renamings is still safe. Note, however, that a failed rollback cannot be automatically salvaged.
- Authors: Aristide Grange and Alexandre Perlmutter.
- macOS GUI: Platypus, by Sveinbjorn Thordarson.
- Cross-plaform filename check: Python library
pathvalidate, by Tsuyoshi Hombashi.