If you open Dolphin in a not indexed folder semantic search is not working at all even when you press "Everywhere" button. Reproducible: Always Steps to Reproduce: 1. Open Dolphin in a indexed location. 2. Use Find to locate files with Everywhere enabled. 3. Close Dolphin and open it in a not indexed location. 4. Test your previous search. Actual Results: Semantic search is not working. Expected Results: If you have Everywhere enabled semantic search must work.
Thanks for the report. I guess that changing this makes sense.
Hm, I thought about this again. If a user disabled Baloo by adding the home folder to the excluded folders, then searching "Everywhere" will now trigger a "filenamesearch" in the home directory. It may be slow, but it works. If we would implement your suggestion, then searching "Everywhere" would stop working for these users. This might be worse than having a non-semantic search when searching "Everywhere" while in a non-indexed location. One could in principle check if the home folder is excluded from indexing, but this would result in rather fragile code, and I'm not sure if this bug is important enough to justify taking any risks. Could you describe a common use case which involves starting a search in a non-indexed location and requires a Baloo search?
In my opinion, if you enable "Everywhere", you must search always with Baloo and if there is no semantic results, then you must launch filenamesearch. This was a fast search with Nepomuk so with Baloo must be fastest. I don't know if this is a common use case but I work in multiuser computers so not all my files are in my Home. On the other side I'm not indexing all my Home, in fact I'm only indexing a few places, so search with Dolphin is useless. And, off course, there is a method to exclude folders. An about filenamesearch, this could be an interesting feature for someone with few files in his home directory. In my case, with more than 3 million files, and counting, filenamesearch is annoying and I miss a method to totally disabled it.
Thanks for the update. (In reply to comment #3) > In my opinion, if you enable "Everywhere", you must search always with Baloo > and if there is no semantic results, then you must launch filenamesearch. Well, waiting if the baloo search returns anything and then starting a filenamesearch if that is not the case is not really possible without ugly hacks and adding quite a bit of bug-prone code. I don't think that it is what is wanted in most cases either. There may be search terms for which you simply can't find anything, and then running a very slow filenamesearch everywhere is not the right thing to do. The only possible solution (not pretty and not perfect though) that I can see at the moment is to ask Baloo if the home folder is excluded from indexing, and always use baloosearch for "everywhere" searches if that is not the case. > An about filenamesearch, this could be an interesting feature for someone > with few files in his home directory. Yes, and there really are users who have few files only and disable Baloo, and they expect that the search works for them.
It could be https://bugzilla.redhat.com/show_bug.cgi?id=1146980 but I disabled the KDE semantic search
Confirming on Plasma 5.10
Confirmed in Plasma 5.17. Content search now refuses to work ANYWHERE. Oh, wait, it works on KDE4. Its been a year and a half guys...
This seems to work as expected in Dolphin 16.12.3 and 17.08.0. In a folder that's not indexed, or where the indexing isn't finished yet, it falls back to the slow filename search for me.