Remember "Rename Items" settings

Bulk renaming is always set to Enumerate. If you want to Replace Text or Add Text you have to pick it from the drop down menu every time.

It would be nice if there was either a checkbox for “use this as default” or simply it opening up with the setting that was last used.

As someone who’s using Replace Text multiple times on the daily, Add Text sometimes, and never had use for Enumerate, that little reset of settings every time is a real time thief (or feels like it at least, maybe it’s just a mood thief).

3 Likes

Good suggestion.

I was the original author of the new bulk operations and this selector.

Should it be permanent until the user change uses a new rename operation, or should it be only for the dolphin instance lifetime ?

I am guessing permanent.

1 Like

Would you mind opening a feature request on bugs.kde.org for kio.

Brainstorms here are not durable enough.

Reading this thread made me realize that I’ve also thought such a feature would be helpful - I opened a feature request for tracking: https://bugs.kde.org/show_bug.cgi?id=523932

2 Likes

As someone who uses all three rename operations a lot, I just wanted to add I really like the way it currently works. I usually use the mouse wheel to scroll the dropdown to the one I need right now (or know just to type a few ###s for the default), which is a lot easier if it always starts with the same one.
Having to check which operation was selected last would in turn make it my workflow a lot less smooth, so I don’t see this as a general upgrade at all.

Wonderful
It’s a great tool :pinched_fingers:

And yes, I think permanent would be best, probably just confusing if not permanent.

I see @johnandmegh have created one, so I won’t make a copy. Cheers!

perhaps a user settable default option/“remember” option is better considering amilias input.

1 Like

Settings only when ABSOLUTELY necessary. A simple consistent behavior is preferable.
I won’t consider it here.

1 Like

Suspected that was the approach regarding Dolphin.

Then I keep advocating for last-used memory - and as a counter to amilias standpoint: If one take all pairs of subsequent uses of the rename tool by all users; I’d wager the amount of repeated use of the same rename-function twice is vastly greater than the amount of times it’s two different functions used. Like 1:100 vast.

I’m sure you realize yourself that making up statistics out of thin air is no basis for any sort of discussion, so you could’ve just said that you don’t actually care about hearing deviating opinions in the first place.

It’s just a wager about statistics, since KDE thankfully doesn’t collect that data to make the statistics, as we all know.
I’d say opposite: if there was data, facts, known truths, there wouldn’t be as much need for discussion. But when we need to extrapolate from insufficient data, a discussion is more needed.

It’s just an estimated guess based on my limited knowledge of human behavior patterns. To rudely bring in the rest of the world into consideration even though they’re not in this thread.
If one wants more than a 4-way vote (not that it is a vote, but you know what I mean).

On the contrary you’re more than welcome to refute my estimate on user behavior.
Perhaps my basis doesn’t translate to this function at all, because something I’ve missed or didn’t think of, etc.

Like your usecase, I wouldn’t have thought of it at all on my own.

It really really has nothing at all about not wanting to hear your (or opposite) opinions, but since it’s there, (and it hasn’t changed mine) I want to put more into favor of mine.
But in this case it was mostly just to make clear I still think memory is a good idea, after the setting-discussion.

If you NEED that file extension “may not work again” safety thing disabled forever, then follow this.

Go to Properties.

In the name field backspace the file extension and type a new one.

Click OK.

This will trigger the bug in Properties that does not give the warning. hopefully KDE never fixes this.

FYI, I just landed a fix for this bug, will be in KDE Frameworks 6.30 scheduled for September 11th.

6.29 is around the corner, so this couldn’t make it there.

2 Likes

I would say permanent. Remember latest setting.