https://bugs.kde.org/show_bug.cgi?id=445825
--- Comment #3 from tagwer...@innerjoin.org ---
(In reply to saif1988 from comment #2)
> Yes, this is using baloo.
The test I tried was - pausing a second or so between each to allow baloo to
keep up:
$ echo "Hello Penguin" > test-codex.txt
$ echo "Hello Codex" > test-penguin.txt
$ baloosearch penguin
$ baloosearch codex
and then:
$ echo "Hello Codex" > test-penguin.txt
$ echo "Hello Penguin" > test-codex.txt
$ baloosearch penguin
$ baloosearch codex
I was getting the "last file written" listed first...
(done on Neon Testing)
> Because if we think that the solution to this problem is to manually typing
> "filename:codex" to bring the result, then this bug report would be
> discarded as a design choice. I really hope it doesn't, because to me it
> clearly is an unintended bug to return such "poor" search results.
I've just looked through "System Settings > Search > Krunner" to see if there
was a configuration option to do "just" filename search. I don't see one and
maybe that would be useful...
I thought I saw a comment somewhere about "mixed case" searches, there's been
some confusion/uncertainty with krunner results, Bug 388857 - scroll down to
the 14th comment
--
You are receiving this mail because:
You are watching all bug changes.
