https://bugs.kde.org/show_bug.cgi?id=413709
--- Comment #3 from TigerShark <ties...@yahoo.com.ar> --- First time I hear about fish shell. Will give it a try. Didn't understand the related PR. Setting that history to 0 would disable the auto completion? If so, it could function as some kind of workaround I guess. I might be repeating myself but let me go over the idea again. I'm in no way against offering auto-completion, just against suggestions being automatically "accepted" and searched for without user confirmation by pressing Tab (or right arrow maybe). Automatically searching for suggestions saves the user exactly 1 keystroke (tab|→) when the suggestion is what the user actually intended. On the other hand, it forces the user to input 1 or more characters to "correct" every wrong suggestion. Given krunner can search in a lot of places, I dare to say the probability of several entries having matching starts is high. That in turn means the average amount of keystrokes needed to correct the auto-completion suggestion will be higher or equal to just typing a bare minimum and then pressing down|down|down to get to the correct entry. I guess the mental effort to check the auto-completion is right is not less than the required to find that the 4th entry in the list is the correct one. Ofc I don't have the data to back this up, just my personal experience and observations. Ideally, I would expect krunner to search for what I explicitly type. Results are sorted by whatever history count (or machine learning?) algorithm u currently use, but with a setting to force use alphabetical order (no idea if this already exists). Auto completion requires a tab press to apply its suggestion and update the search query. Thx for your interest in this report ;) -- You are receiving this mail because: You are watching all bug changes.
