Bug 168215 - Only run a command, no searching or autocompletion
Summary: Only run a command, no searching or autocompletion
Status: RESOLVED DUPLICATE of bug 376666
Alias: None
Product: krunner
Classification: Plasma
Component: general (show other bugs)
Version: unspecified
Platform: Debian testing Linux
: NOR wishlist
Target Milestone: ---
Assignee: Plasma Bugs List
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2008-08-03 15:00 UTC by Torquil Macdonald Sørensen
Modified: 2020-07-11 15:16 UTC (History)
6 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 Torquil Macdonald Sørensen 2008-08-03 15:00:57 UTC 
Version:            (using KDE 4.1.0)
Installed from:    Debian testing/unstable Packages

I would like krunner to only run the command that I write, with no autocompletion and no search results. I tried to disable everything but the "Command line" plugin, but it still displays icons with search results.

Best regards,
Torquil Sørensen
Comment 1 Stephan Sokolow 2009-02-07 08:47:28 UTC 
Probably a good idea as an option... especially for people on older systems.
Comment 2 Håkon T 2009-02-10 12:54:04 UTC 
This would probably fix #180115 as well.
Comment 3 Kai Uwe Broulik 2010-08-31 06:30:44 UTC 
There should be an additional keyboard shortcut, e.g. alt+shift+f2 for opening krunner in a “run only mode”.
Comment 4 Kai Uwe Broulik 2011-01-04 23:58:06 UTC 
*** This bug has been confirmed by popular vote. ***
Comment 5 Sergey Kondakov 2012-03-12 06:21:49 UTC 
And i would like that thing also not to filter my input and launch stuff exactly as i typed, including env.vars and scripting. Or, even better, not to be on my desktop in the first place.
Comment 6 Alexander Lohnau 2020-07-11 15:16:12 UTC 
Also for just using one plugin the single runner mode can be useful (in case you still want to use the other plugins from time to time). But that is currently broken, see BUG 374518.

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