There are actions and one can use the command line for opening KRename with files, but there are no command line args (or action) to make the rename about the folders itself (while optionally ignoring their contents).
I need this option too.
In my version (5.0.2) when you click "Add" button, you can enable "Add only folder names" or even "Add folder names and filenames", so I think this question is solved yet (but no one answered about).
This is not about the UI, but about the CLI.
(In reply to Mihai Sorin Dobrescu from comment #3) > This is not about the UI, but about the CLI. My fault, I didn't know it was possible to use krename from CLI only. I see there are not same options, but understand that so many features are difficult to bring to CLI use.
CLI is the one to be called in a Dolphin/KDE menu service. Well, almost. A parameter needs to be set in the a CLI command to start it one way or another. Look here: https://github.com/KDE/krename/blob/015e995690bde126bfbec304e99eee973402269e/src/servicemenus/krename_dir_rec.desktop#L8 : Exec=krename -r %U To open it on a dir, '%U' is enough. To be recursive, it needs '-r'. So it's like a bridge between CLI and GUI to be launched from GUI in a specific directory.
Very interesting. But, why not to use open "Konsole" from "Dolphin" in that folder and use a command like "rename -r" to do same task? In fact, we'll need something more powerfull like "find . -type f -name "*" | xargs -r rename -nv 'whatever regular expression you need" but I think that if I need to use a terminal to launch a GUI application, something is not going well .... Sometimes I use from "Krunner" sentences like "kdesu kate path_to_file_and_filename" to edit root required files (as "fstab" but cause it's necessary to open files as root. Do not require parameters I think that add parameters options to GUI applications when there are equivalents ways to do it with Linux commands, is work overload. But is my opinion.
I'd love to be able to automate in command line as well.
(In reply to Mihai Sorin Dobrescu from comment #7) > I'd love to be able to automate in command line as well. Anyway, you have reason. "Service menu" is underrated by Plasma developers. Users like you create these services and share them with others. However, over time, changes to the Plasma libraries may cause them not to work. If the user who created them can no longer check if they work, they remain available and fail when trying to install them (I have had this happen to some of them). KDE should take note of these useful services you create and incorporate them into the desktop installation itself or at least update them according to libraries changes .
(In reply to Rafael Linux User from comment #8) I don't feel the services menu is underrated. I have some scripts I launch through that since many years ago and they still work without any problem. It's a handy way to start processing files.
Not underrated by you, but by KDE ;)