https://bugs.kde.org/show_bug.cgi?id=405094
--- Comment #3 from Igor Poboiko <igor.pobo...@gmail.com> --- It's not my logic, it's the logic of Baloo and its original developer :) The logic is quite straightforward though. Most likely, user is searching for some particular document. If his search term is contained in "137K files", it wouldn't help at all - such term might as well be dropped. If those are only terms user looking for, he won't be able to find anything; if his query contains other terms, those will more likely to help Baloo identify the document user is looking for. I believe short terms are mostly there just to be able to search over filename extensions (like "filename.jpg") and e-mail/domains (like "john...@example.org"). In both cases, the "exact match" logic would suffice. > [...] Apparently A-Z characters are first class citizens, whereas the other > characters are estranged cousins. That's intentional. Remember that Baloo provides search over file contents too. And if you have it in mind, it doesn't sound that arbitrary: letters and words (not necessarily A-Z: also numbers and other languages) contain the most information to build index upon. What are the chances user is going to search for a document that has "." or " " or "_" somewhere inside? And what are the chances it will help to identify the document uniquely? Not to mention that by restricting itself to alphabet, it reduces the size of the index by a large factor. If you're looking for a file with a name you know precisely, and which mostly contains non-alphanumeric characters, then "find" / KFind or any other filesystem crawler will most likely do better. > Baloo = 5.55.0 I couldn't also help but notice that the version your distribution ships is a bit outdated. There were large number of improvements to Baloo somewhat around 5.60+ (unrelated to this particular issue, though). -- You are receiving this mail because: You are watching all bug changes.
