https://bugs.kde.org/show_bug.cgi?id=427455
--- Comment #3 from Thiago Sueto <herzensch...@gmail.com> --- Well, I can't argue with that: it is a personal preference. I just thought it would work well as opposed to something like "Just disable default content indexing", which is what openSUSE has been doing for a while. Baloo has been in a vicious cycle where a common workaround is to disable it entirely instead of reporting bugs, and without reporting bugs users keep complaining about issues they face, further harming its image and motivating others to disable it. So I assumed changing the defaults could improve this situation, even if not my specific suggestion, so I don't mind if this bug report is closed if you think the current situation is alright. As for your points: > No. Users already complain if baloo does not find files below '/'. I recall that one, but that's definitely something that takes quite a while to index and uses a bunch of resources. I wouldn't personally see it as a good move for defaults since this might render at least half an hour of indexing after login (haven't really tested this to see the time spent on indexing). It's more the kind of thing that the user should choose to do knowing the consequences instead. > > * Less bug reports regarding unexpected files provided by random > > applications that shouldn't be indexed to begin with. > > These files may be located anywhere. I agree, but my point was more about priority/likelihood. I lack the data, but I'd assume people populate their Documents and Music folders with searchable items more than home itself. I'd also assume that config files are less likely to be searched. If priority/likelihood is irrelevant here, my whole suggestion is irrelevant too. > > * Less file types that could cause issues to baloo. > > Unrelated. If there is a problem with some file type, file a bug. Again, > these files may be also located unter e.g. Documents. I agree, it can happen anywhere. Just the likelihood might be different, as mentioned above. > > * The search KCM won't have a one- or two-item list under "Folder specific > > configuration". > > Why is this bad? This is not bad, but it could be friendlier. Having more default suggested folders that can be toggled by two clicks is certainly more inviting to use than adding each individual folder manually. Extra folders could still be added. If anything, I'd like to see this specific suggestion, even if the rest isn't done. What do you think? > > * Because the search KCM is more populated, users would feel more compelled > > to check the interface and improve baloo filters since it's just two clicks > > in a combobox. > > * For further making it easier for users, adding the folder .config as "Not > > indexed" to "Folder specific configuration" would be useful both for the > > above and to make the setting "Index hidden files and folders" more > > meaningful. > > * Technical users and developers won't suffer from this since they can just > > configure specific folders to index. > > You can just disable indexing $HOME and add Documents etc. I am one of those technical users, so it is not an issue to me personally. I'm just suggesting things. -- You are receiving this mail because: You are watching all bug changes.
