https://bugs.kde.org/show_bug.cgi?id=499078
cwo <[email protected]> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |[email protected] --- Comment #4 from cwo <[email protected]> --- The history thing is quite confusing in wording and behavior. It mixes two things: the history display, and the way completions work. History (at least a global one) is always kept, even if disabled. When it's set to disabled, it will open the history when pressing Arrow Down on the query field while it's empty, but not show the expander in the search field that allows you to show/hide it by clicking. When it's set to "suggestion", it will work on Arrow Down, show the expander in the search field, and show a completion of the current search term in a different color (but not automatically search for that term until the user presses Tab or Arrow Right. When it's set to "auto-complete", it will work on Arrow Down, show the expander in the search field, and automatically complete the term and search for it (but it's selected in such a way that the user can continue typing as if there was no completion if they want to). The last query from the running session is always kept, no matter the setting. The suggestion/autocomplete setting sort of makes sense (though it seems rather minor). The way the history dropdown works with history disabled doesn't to me - why keep one way of showing it and not the other? It feels like when history is disabled, it shouldn't keep history at all, and at least never show it. I'm not sure a "Enable history dropdown, but don't suggest/complete from it" option is necessary (as the suggestion seems so unobtrusive), but we currently sort-of offer it inconsistently. -- You are receiving this mail because: You are watching all bug changes.
