https://bugs.kde.org/show_bug.cgi?id=490972
--- Comment #17 from Adam Fontenot <adam.m.fontenot+...@gmail.com> --- Something I noticed which is contributing to the impact of this problem with the Search widget: * Unlike krunner, Search does not auto complete previous searches. When I type "se" into krunner, I get a complete set of results because it autocompletes a previous search. "se" in the Search widget shows nothing. * For some reason, searching in the Application Launcher widget is *much* faster than searching in the Search widget, despite the fact that they seem to (?) use the same search backend and have the same settings (and both show some file results). This is frustrating as Search seems like the simpler tool. This is a big enough difference that it's *very* easy to see: Application Launcher has search results available instantly before my fingers can even come off the keys, Search takes probably 0.4 seconds to show results. When you're already "waiting" for results because of this issue, another 0.4 seconds makes it feel much worse. Happy to report either / both of these as separate issues, but it's not clear to me that they are issues. Mentioning them here because I realized when trying out these other widgets today that this bug bothers me much less when using them than my usual search widget (Search). -- You are receiving this mail because: You are watching all bug changes.
