[dolphin] [Bug 488626] Please make Dolphin hide 'lost+found' dirs by default, just like Thunar does

Felix Ernst bugzilla_noreply at kde.org
Mon Jun 24 14:18:02 BST 2024


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

--- Comment #5 from Felix Ernst <felixernst at kde.org> ---
(In reply to Eduard from comment #4)
>Thanks for the detailed reply!

You are welcome!

>Now that's solved too with .hidden.

I am glad to hear that!

> However, that gives a lot of specific control per directory, but it wouldn't
> be great if Dolphin had a general configuration option for this too? But
> lower priority wish, I get it.

It's a bit too niche I think. Creating such a .hidden file is quite easy and
one only has to do it once per file system. As a general option for hiding we
have already recently added a setting in Dolphin's settings dialog to hide
application/x-trash mime types. Users can already modify that any file
extension belongs to that mime type and hide them this way. And I don't want to
be too eager to hide that folder either because it can be very important for
recovering data. Actually, it might make more sense to bother the developers of
the fsck utility to not create such folders in the first place. That's on them
after all (https://www.baeldung.com/linux/lost-found-directory) and
conceptually it seems easier to me to not create a random empty folder when it
isn't needed rather than have every application that shows folders to hide it.

Dolphin provides various ways of hiding already and we do inform about them in
the extended help text of the Dolphin hiding feature. I think we should have
most workflows covered this way. There are unfortuantely sometimes aspects
which are so custom and specific to users that adding a general setting for
them is too much trouble and therefore leads to more issues in the long term
than it helps.

> And then I am going to have that same wish for Thunar as well. :P

Well, don't get your hopes up! I am not sure the Thunar devs are keen on
implementing such a feature either. 😅

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


More information about the kfm-devel mailing list