Bug 445159

Summary:	command line executable should be started in a terminal by default
Product:	[Plasma] krunner	Reporter:	elypter <elypter>
Component:	general	Assignee:	Alexander Lohnau <alexander.lohnau>
Status:	CONFIRMED ---
Severity:	wishlist	CC:	elypter, ktchidev, nate, plasma-bugs
Priority:	NOR	Keywords:	usability
Version:	unspecified
Target Milestone:	---
Platform:	Other
OS:	Other
See Also:	https://bugs.kde.org/show_bug.cgi?id=446169
Latest Commit:		Version Fixed In:
Sentry Crash Report:

Description elypter 2021-11-08 13:50:55 UTC

i just found out that you can launch text based applications in a terminal by pressing shift+enter from this report https://bugs.kde.org/show_bug.cgi?id=437131

this should be the default behavior.  most of the time you want to see a result or make sure something executed properly. its a way more common use case and should be triggered simply by hitting enter. 

it would be great if that behavior was switched or if there was a settings page where you can change it.

Comment 1 Nate Graham 2021-11-08 23:30:45 UTC

It's not the worst idea. If you run a command in KRunner that produces output rather than doing something specific, it will look like nothing has happened.

What do you think, Alexander? "Run silently" could still be bound to Ctrl+Enter for experts who want that.

Comment 2 Nate Graham 2021-11-15 19:42:03 UTC

*** Bug 445322 has been marked as a duplicate of this bug. ***

Comment 3 Alexander Lohnau 2021-11-15 19:52:11 UTC

Currently there are still CLI options offered for some GUI applications. That is due to issues with the KRunner de-duplication, where I have fixed the root cause. I guess once that is figured out, switching the default will make sense. (Take VSCode as an example, typing "code" will produce the shell command as first result).

Comment 4 Nate Graham 2021-11-16 14:56:01 UTC

Gross, why is that? A bug in VS Code's desktop file?