I meant this function: https://bugs.kde.org/show_bug.cgi?id=404955

Well, now we're in that awkward situation where user A asks for something reasonable, and we implement it, and user B says it's a regression for them, also using reasonable arguments.

So our options are to:
- Revert the change and make user A mad
- Tell user B to live with it, making them mad
- Somehow make it configurable, cluttering up the UI with options 99.9% of people will never care about (though maybe this could be mitigated by putting it in a context menu somewhere)
- Implement a complicated heuristic to guess which elision mode will be more useful based on the text, running the risk of trying to be so smart that it ends up dumb and satisfies nobody

Elvis, what are your thoughts? As you're the maintainer, I'll abide by your decision.

Yes, my suggestion was just to make it configurable. It's just one checkbox))

(In reply to Nate Graham from comment #2)
> Well, now we're in that awkward situation where user A asks for something
> reasonable, and we implement it, and user B says it's a regression for them,
> also using reasonable arguments.
> 
> So our options are to:
> - Revert the change and make user A mad
> - Tell user B to live with it, making them mad
> - Somehow make it configurable, cluttering up the UI with options 99.9% of
> people will never care about (though maybe this could be mitigated by
> putting it in a context menu somewhere)
> - Implement a complicated heuristic to guess which elision mode will be more
> useful based on the text, running the risk of trying to be so smart that it
> ends up dumb and satisfies nobody
> 
> Elvis, what are your thoughts? As you're the maintainer, I'll abide by your
> decision.

I don't want to be that guy, but... I told you so ;)

Reverting is not an option for now. We can reconsider if enough people complain about the new behavior. So I'd keep this ticket open waiting for more feedback.

If a configuration option isn't planned, here are some suggestions:

With the filename extensions now visible, I suggest to hide the Type column to get more room for the Name column. Maybe it could automatically decide where to elide based on the visibility of the Type column.

Also, to show the extension, middle-elision isn't ideal. It could elide at the point where the extension starts.

What about "Extension" column in addition to "Name", "Type", "Size" and other columns?

I admit it, you did warn me about this, and you were right. :)

In reply to Christoph Feck from comment #5)
> Also, to show the extension, middle-elision isn't ideal. It could elide at
> the point where the extension starts.
That's not a bad idea at all.

Vote for having it be configurable.  Radiobuttons for "Elide At: Middle vs End."

I use a similar naming convention to Matteo M (in the other thread), & this behavior makes it impossible to get consistent behavior across systems.  aka if I name my files such that the important information is visible on Windows & elsewhere, Dolphin hides the important part.  If I name it for Dolphin, the important part is hidden everywhere else.

Having an option is a simple solution that satisfies everyone: those who want it & those who don't.

We have a new approach in Dolphin 20.08: we right-elide as before, but always show the extension after the elided text.

Let's see if that makes people feel better, and then if not, we can either make it configurable or revert the change altogether.

That would be a great solution, if it's also possible to hide the extension? (Confusingly, that's actually the title of this issue - "Please, add option to disable "filename extesions are always visible?").  If the extension is always visible though, it's unfortunately just as problematic, because it would still cause the extension's 4 characters of "not configurable text" to hide 4 characters of "useful/configurable" text. Just like the previous solution.