SUMMARY The command line plugin is enabled by default (atleast on my install), but is not very useful and takes priority over other legitimate searches. For example, if I was searching for `pamac`, which is my package manager, to open the GUI for it, the command line source will take priority and then run `pamac`, which does absolutely nothing except print `--help`. Infact, most command line utilities, when called with no args, seem to just print help to stdout and do nothing. This means in most scenarios the Command Line plugin actually just does nothing when running a command. This is pretty poor UX, but the more pressing issue is that it takes priority over other legitimate searches! I'm not sure whether this should be considered a fundamental flaw in the plugin, maybe some people are getting some legitimate use out of it. However, I think it should atleast be considered to be disabled by default, as it has unintuitive behaviour and negatively interacts with other parts of the application. STEPS TO REPRODUCE 1. Search for something that also happens to be a binary on your system. 2. If your search exactly matches that binary, it will take priority over the other thing you're searching for. 3. Hitting enter will instead will run that binary. Typically binaries ran with no arguments print help info to stdout, so this does nothing, and means you don't open what you wanted to! OBSERVED RESULT N/A EXPECTED RESULT N/A SOFTWARE/OS VERSIONS Windows: macOS: Linux/KDE Plasma: (available in About System) KDE Plasma Version: KDE Frameworks Version: Qt Version: ADDITIONAL INFORMATION N/A
What version of Plasma are you using? The first issue was supposed to have been fixed a few releases ago. The second issue is Bug 445159.
(In reply to Nate Graham from comment #1) > What version of Plasma are you using? The first issue was supposed to have > been fixed a few releases ago. > > The second issue is Bug 445159. Ah sorry I missed that part of the form. KDE Plasma Version: 5.22.5 KDE Frameworks Version: 5.87.0 Qt Version: 5.15.2
Yup, it was fixed in 5.23. :) *** This bug has been marked as a duplicate of bug 445159 ***