[krunner] [Bug 482196] History setting not effective
https://bugs.kde.org/show_bug.cgi?id=482196 Nicolas Fella changed: What|Removed |Added CC||nicolas.fe...@gmx.de Version|5.93.0 |6.0.0 -- You are receiving this mail because: You are watching all bug changes.
[krunner] [Bug 482196] History setting not effective
https://bugs.kde.org/show_bug.cgi?id=482196 --- Comment #3 from Andrew Brouwers --- Created attachment 166311 --> https://bugs.kde.org/attachment.cgi?id=166311=edit konsole launched, while "kons" retained in a future krunner instance -- You are receiving this mail because: You are watching all bug changes.
[krunner] [Bug 482196] History setting not effective
https://bugs.kde.org/show_bug.cgi?id=482196 --- Comment #2 from Andrew Brouwers --- (In reply to Alexander Lohnau from comment #1) > Hmm, I am not sure how to handle this. It is not any persistent history, but > just your last typed query. In case a window opens and KRunner closes, you > might otherwise miss your previously typed text. Though you should be able > to override the text with just one keystroke. > > A sensible differentiation might be the cause for closing KRunner. Like the > escape key could be handled separately and clear the text when a match is > run. Though I am not sure if this behavior seems consistent to the average > user. I should clarify, even if I type "kons," hit "enter" once konsole is highlighted (ie, it didn't get interrupted, but rather successfully launched my searched-for app), it *still* shows in my history. The history setting just seems broken in plasma 6. -- You are receiving this mail because: You are watching all bug changes.
[krunner] [Bug 482196] History setting not effective
https://bugs.kde.org/show_bug.cgi?id=482196 --- Comment #1 from Alexander Lohnau --- Hmm, I am not sure how to handle this. It is not any persistent history, but just your last typed query. In case a window opens and KRunner closes, you might otherwise miss your previously typed text. Though you should be able to override the text with just one keystroke. A sensible differentiation might be the cause for closing KRunner. Like the escape key could be handled separately and clear the text when a match is run. Though I am not sure if this behavior seems consistent to the average user. -- You are receiving this mail because: You are watching all bug changes.
