Plasma application launchers/es: Difference between revisions
(Updating to match new version of source page) |
(Updating to match new version of source page) |
||
Line 39: | Line 39: | ||
:There is also [[Special:myLanguage/KRunner|KRunner]], which replaces the "run command" dialog, blurs the lines between task manager, desktop search, application launcher and command executor and provides a quick way to run applications or open documents among other things. | :There is also [[Special:myLanguage/KRunner|KRunner]], which replaces the "run command" dialog, blurs the lines between task manager, desktop search, application launcher and command executor and provides a quick way to run applications or open documents among other things. | ||
|} | |} | ||
<span id="How to change the application launcher"></span> | |||
== How to change the application launcher | == How to change the application launcher == | ||
To change the application launcher, right click on your current launcher and select <menuchoice>Alternatives…</menuchoice> | To change the application launcher, right click on your current launcher and select <menuchoice>Alternatives…</menuchoice> |
Revision as of 07:50, 6 July 2019
En Plasma hay distintos lanzadores de aplicaciones o "menús de inicio", entre los que se incluyen:
Application Launcher
| |
Application Dashboard
| |
Application Menu
| |
Lancelot
| |
Homerun
| |
KRunner
|
How to change the application launcher
To change the application launcher, right click on your current launcher and select
Next, choose the launcher you want to use.
How do I change which key opens the application launcher?
It's possible to do that in two ways: you may right click on your current launcher and select
, selecting the tab , clicking on the button and then typing the combination you want to use as keyboard shortcut.You can also use
→ → → → .And if you ever want to restore the default Meta key, you can use the combination Alt+F1, which serves this exact purpose.
I can't bind the Meta key to open the Application Launcher anymore!
This issue may occur because of the way KWin binds keys. Please refer to this section.