Describe the bug
When using --select-tab, --split-vertical (or --split-horizontal) and --execute-command, guake selects correct tab, split screen but not execute desired command on new area. Instead, execute command on new tab.
Expected behavior
This behavior worked on previous versions (before remove of execute-command and later reinclusion of this option).
Actual behavior
guake selects desired tab, split tab content but run command on new tab.
What you actually get.
Tab open, splited and not command running on it. Other tab with desired command running.
--execute-command was removed in a previous version because it enabled a security flaw, which could be avoided by only allowing the flag to run on new tabs, so it was brought back with altered behavior in a later version. Although I guess this specific scenario where the flag is combined with split- should be fine to allow not making a new tab since it's still spawning a new terminal in the split screen.
Can't allow for selecting an existing terminal after the split to run the command in an already running terminal though, as that would reintroduce the security flaw
Instaled from ppa
Describe the bug When using --select-tab, --split-vertical (or --split-horizontal) and --execute-command, guake selects correct tab, split screen but not execute desired command on new area. Instead, execute command on new tab.
Expected behavior This behavior worked on previous versions (before remove of execute-command and later reinclusion of this option).
Actual behavior guake selects desired tab, split tab content but run command on new tab.
What you actually get. Tab open, splited and not command running on it. Other tab with desired command running.
To Reproduce
Screenshots
$ guake --support
Guake Version: 3.9.0 Vte Version: 0.68.0 Vte Runtime Version: 0.68.0 -------------------------------------------------- GTK+ Version: 3.24.33 GDK Backend:--execute-command
was removed in a previous version because it enabled a security flaw, which could be avoided by only allowing the flag to run on new tabs, so it was brought back with altered behavior in a later version. Although I guess this specific scenario where the flag is combined withsplit-
should be fine to allow not making a new tab since it's still spawning a new terminal in the split screen.Can't allow for selecting an existing terminal after the split to run the command in an already running terminal though, as that would reintroduce the security flaw