Bug 173598 - krunner should consider all the input before interpreting the "Enter" key
Summary: krunner should consider all the input before interpreting the "Enter" key
Status: RESOLVED DUPLICATE of bug 169283
Alias: None
Product: krunner
Classification: Plasma
Component: general (show other bugs)
Version: unspecified
Platform: unspecified Unspecified
: NOR normal
Target Milestone: ---
Assignee: Plasma Bugs List
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2008-10-26 15:58 UTC by Sylvain Joyeux
Modified: 2008-12-20 21:03 UTC (History)
2 users (show)

See Also:
Latest Commit:
Version Fixed In:
Sentry Crash Report:

Attachments
Add an attachment

Note You need to log in before you can comment on or make changes to this bug.
Description Sylvain Joyeux 2008-10-26 15:58:44 UTC 
Version:            (using KDE 4.1.2)
Installed from:    Unlisted Binary Package

I have slow computers, and on them I type faster than krunner's search. This leads to the following:

  I type "konsole<CR>"

KRunner starts konqueror, because it has interpreted "kon<CR>", i.e. it did not search for the whole input, but interprets <CR> with whatever search result it has at the moment. 

Obviously, if I type "konsole", I don't want krunner to start something totally unrelated to it, so it is IMO a bug.
Comment 1 Eduard Sukharev 2008-10-26 16:09:30 UTC 
On my EeePC it also happens from time to time - really annoying. For now i just type "ons" for konsole.
Comment 2 FiNeX 2008-12-20 21:03:58 UTC 

*** This bug has been marked as a duplicate of bug 169283 ***