Version: unspecified (using KDE 4.7.1) OS: Linux It would be great, if it was possible to define aliases in krunner. For example: instead of typing "screen brightness 100" one could configure an alias and run "sb 100". or "ff" instead of "firefox", "k" instead of "konsole", and so on. Do you understand what I am trying to say or should I elaborate? What do you think? Reproducible: Didn't try Expected Results: It's possible to configure custom aliases though KRunners configuration dialog
To cut my long-winded explanation short: A similiar concept to bash aliases in krunner would be great.
I'd also like to see this, but from a different approach: I'd like to see krunner support bash aliases and/or functions directly, that way I can leverage my already existing functions without needing to do anything special for krunner. Plus, krunner itself wouldn't need to do anything more than, say, source ~/.bashrc on startup. Should be an easy change, and would be quite convenient for users, as opposed to the current need to launch a terminal to run aliases/functions.
there is a ca. 5 line python demo of a krunner-plugin, which could be adapted to perform such a task. easy to test.
Extra aliases for krunner seem a bit off to be, but what Jared B. described makes sense and should be doable!
A possibly relevant merge request was started @ https://invent.kde.org/plasma/plasma-workspace/-/merge_requests/202
Just to add to that; one can create aliases another way: Custom .desktop entries (either through kmenuedit or manually) will be shown in krunner. An extra advantage of that is you can then also easily assign global shortcuts as well as have more readable names. I would support any UX to try and surface that more - so we're building towards a common platform that reuses the tech we have, rather than adding layers on top.
(In reply to David Edmundson from comment #6) > Just to add to that; one can create aliases another way: > > Custom .desktop entries (either through kmenuedit or manually) will be shown > in krunner. But that is a different usacase. With aliases you can easily add another flag to it or pipe the output to another program etc. Your suggestion goes in the direction of BUG 396881. > I would support any UX to try and surface that more - so we're building > towards a common platform that reuses the tech we have, rather than adding > layers on top. Because we are reusing the already existing aliases I would not say that we are adding layers on top ;-)
*** Bug 195392 has been marked as a duplicate of this bug. ***