[konsole] [Bug 377412] konsole with -e option breaks previous usage--now requires to specify shell to execute commands

Michael bugzilla_noreply at kde.org
Wed Nov 25 03:43:08 GMT 2020


https://bugs.kde.org/show_bug.cgi?id=377412

--- Comment #20 from Michael <kde at callthecomputerdoctor.com> ---
> The reason is simple I think:
> AFAIK "konsole -e xxx" just runs the command directly and passes it the rest of the line as 
> arguments.
> But the '&&' or ';' are to be parsed by the shell, neither konsole nor the
> application it runs cares about them.

Yes, but I've put the example commands in single quotes so that the arguments
are not pre-parsed before the new terminal window receives it:

> $ xterm   -e 'echo "hello"; sleep 3'
> $ konsole -e 'echo "hello"; sleep 3'

I still don't see why both of these terminals behave so dramatically
differently when executing this.

> Btw, that hasn't actually changed recently, I can reproduce the same behavior 
> with konsole 2.14.2 from KDE4...

Okay, must've been further back then.

-- 
You are receiving this mail because:
You are the assignee for the bug.


More information about the konsole-devel mailing list