https://bugs.kde.org/show_bug.cgi?id=391252
Jackson <b...@twosixfour.net> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |b...@twosixfour.net
--- Comment #14 from Jackson <b...@twosixfour.net> ---
(In reply to Stefan Brüns from comment #7)
I hope the decision to not index "." files will be reversed. Here's why.
>> Many users are not even aware of hidden files/directories, and these are not
>> shown by default in e.g. dolphin. IMHO it would be quite awkward if these
>> files showed up during a search.
If Dolphin was made to not show hidden files, then this would make sense. But,
as you point out, hidden files can be made visible. If the user explicitly
enables Dolphin to show hidden files, clearly they are aware of them. What is
"awkward", rather, is when the user cannot find in a search the files and
folders that are plainly visible on the their screen. This causes a bizarre
dissonance: personally, as someone new to KDE, I figured something was wrong
with my system, and spent an hour troubleshooting before seeing this report.
>> Files in hidden directories are only useful for power users/developers,
>> which are typically capable of using e.g. find and grep.
This is incorrect. Sometimes non-power users and non-developers are following
instructions to find or change some config of a frequently used program. A
quick example is found in a comment to a duplicate this bug, where a user was
just trying to change a setting of their application
(https://bugs.kde.org/show_bug.cgi?id=383778#c5). Some people are just trying
to get their work done, and while being somewhat technically capable, aren't
power-users in the sense that they know all the intricacies of the system.
Another example: I use Dropbox to access thousands of files from an employer.
His operation is Windows-only, and uses the trick of putting "." in front of
important files and folders so that Windows shows them at the top of any
hierarchy. I cannot search for those (most important!) folders and their
contents with Dolphin. Yes, I know how to search via other means, but,
honestly, I had to *look up* how to do so with a GUI (I needed to install a
whole other search application!). It's quite confusing to be forced to switch
contexts.
In addition, it's really ok to make things a bit more convenient for power
users so they can search for a file in their... file manager. If a non-power
user turns on hidden files, yes, they can mess things up, but being able to
consistently search for what is visible on the screen does not make it any more
dangerous; it only makes the UI less confusing and more consistent.
I therefore hope you will reconsider adding an option to make Baloo index
"hidden" files. Ideally it would automatically show hidden files when Dolphin
is set to show them, and not show them when Dolphin is not (i.e., the same
behavior in Nautilus; incidentally, this is the only feature I miss about
Nautilus!). No need to mess with settings, everything just works.
But if you still aren't convinced, at least restore the ability to set "index
hidden folders=true" in .config/baloofilerc (as per
https://community.kde.org/Baloo/Configuration), so that those of use searching
around desperately on the internet for a solution can find a simple one
quickly.
Finally, and I hesitate to say this, since it's currently a workaround I use
(please don't remove that too, in case I'm not persuasive enough! :D ), there's
one further inconsistency: I can manually add files to Baloo's index, even
hidden ones. Why not make it a bit easier? Even allowing the indexing of the
content of . folders that are explicitly added with folders[$e]= would be
useful.
Thanks for your time.
--
You are receiving this mail because:
You are watching all bug changes.
