https://bugs.kde.org/show_bug.cgi?id=521101
--- Comment #13 from Matija Šuklje <[email protected]> --- > Yes, I don't think that's a good idea. What if I create ~/Books? The contents > won't be indexed by default. Then I'll have to first notice this, and then > figure out why. That is true. But I argue it is an easier to identify and fix problem to a user than the current situation. Also, what if I create a temp folder in my home, or some app (or language) creates some random non-hidden folders in my home to be able to run – stuff that’s happened to me several times before? Then I need to figure out why I get dozens of false positives and need to potentially clean my index too. The inverse is currently true: Baloo claims it indexes the whole home folder, but silently ignores several filetypes, extensions and folders – all of which is totally opaque to the normal user, and are even poorly (if at all) documented. In my proposal, the default settings are transparent to the user through the easy to find settings and reduce the guesswork. In the current situation, if a file or folder is not indexed, only the most persistent user will go down the rabbit hole why Baloo does not work as intended (by the user). Many more will simply take Baloo for broken or unreliable. Another option would be to have an optional “expert” view for Baloo’s configuration in KCM and let the power users fine-tune the excludes and includes themselves. But that is not exclusive to having sane defaults. -- You are receiving this mail because: You are watching all bug changes.
