Bug 383812

Summary:	Weird search results in KRunner
Product:	[Plasma] krunner	Reporter:	Alexander Mentyu <notuxius>
Component:	general	Assignee:	Kai Uwe Broulik <kde>
Status:	RESOLVED INTENTIONAL
Severity:	normal	CC:	hein
Priority:	NOR
Version:	5.10.4
Target Milestone:	---
Platform:	Netrunner Rolling
OS:	Linux
Latest Commit:		Version Fixed In:
Sentry Crash Report:

Description Alexander Mentyu 2017-08-21 18:05:09 UTC

For example - try to search for 'Discover' app in KRunner:
1. Start KRunner.
2. Type 'd' letter - no 'Discover' in search results.
3. Type 'i' letter - no 'Discover' in search results.
4. Type 's' letter - no 'Discover' in search results.
5. Type 'c' letter - Discover appears in search results.

Expectations from search:
Discover is appearing in search results right after typing of letter 'd'.

Comment 1 Kai Uwe Broulik 2017-08-21 21:27:13 UTC

Well, if search term is too short we don't search through description and other fields, otherwise you end up with a ton of useless results that all just start with a "D". It's always a trade-off.

Comment 2 Eike Hein 2017-08-28 11:12:59 UTC

> if search term is too short

What algorithm is used to determine "short"?

Comment 3 Alexander Mentyu 2017-11-27 17:21:08 UTC

I think 3 letters or more could be a trigger for search or there can be an option for adjusting such functionality (possibly with minimal value of 3) - similarly to 'Minimal word length to complete' in Kate 'Auto Completion' settings

Comment 4 Eike Hein 2017-11-28 10:13:21 UTC

You should be using the new KStringHandler::logicalLength(string)>3 in KCoreAddons now.

This should have done this in KRunner: https://phabricator.kde.org/D8771