https://bugs.kde.org/show_bug.cgi?id=483578
--- Comment #20 from tagwer...@innerjoin.org --- (In reply to Ellie from comment #19) > ... I got it to work by one day finding the Baloo indexing options inside KDE > system settings, and fully turning off baloo there ... That's the GUI way of setting the "Indexing-Enabled" on or off... > Have a look at ~/.config/baloofilerc, if you've disabled Baloo you should see: > > [Basic Settings] > Indexing-Enabled=false Dolphin looks at this config file and decides whether to use Baloo or not. > 1. Let me identify clearly in some way, e.g. when going into the settings to > configure search providers, which search provider is actually used. Let me > pick a different provider in the Dolphin settings if I want that, too. That would be a nice option. There's baloosearch and filenamesearch, if someone came up with a kfilesearch that followed the same API and behaviour it would make sense that Dolphin has an option to use it... > 2. If baloo returns nothing in a folder that clearly isn't empty, maybe > Dolphin could eventually figure out there's some issue with it and display > some sort of warning. The "clearly isn't empty" is troublesome... I don't think you can know whether Baloo is not finding file because you have too tight a search criteria (think of a typo in your search query) or that Baloo has died... > Basically, when baloo is enabled but not working at all, Dolphin doesn't > give the user much to work with to figure out what is going on. I think there's a case for Dolphin asking Baloo if it has indexed that particular folder. If Baloo is alive and can answer "yes" then Dolphin uses the Baloo index, otherwise it falls back to its own (filenamesearch) way of doing things.... -- You are receiving this mail because: You are watching all bug changes.
