https://bugs.kde.org/show_bug.cgi?id=490972
--- Comment #20 from Nate Graham <n...@kde.org> --- I dug into this a bit and came to the conclusion that the problem is KRunner's infrastructure for allowing individual runners to ask for a minimum letter count before they start returning results. Because runners choose different minimum letter counts, the problem is not solvable, and the best we can do is document it by changing the UI of each KRunner-powered search to be clearer about what's going on. But this is a poor result IMO. The whole thing is also not great for Chinese where 1 and 2 character searches could otherwise return useful results. IMO it's a contributor to KRunner's search results feeling awkward and random, and I'd consider it a failure and throw it in the bin. We could port all the runners away from using it, or even change setMinLetterCount() to always return 0 (or both). I experimented with that, and the search results seem… fine? For background information, the minimum letter count system was added in https://invent.kde.org/frameworks/krunner/-/merge_requests/26. -- You are receiving this mail because: You are watching all bug changes.
