[konsole] [Bug 370300] Behaviour of `--separate` and `--new-tab`

Alex Bikadorov bugzilla_noreply at kde.org
Thu Dec 21 20:11:39 UTC 2017


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

Alex Bikadorov <alex.bikadorov at kdemail.net> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
            Version|16.08.1                     |17.08.1

--- Comment #2 from Alex Bikadorov <alex.bikadorov at kdemail.net> ---
>From `konsole --help`:
>"--separate, --nofork       Run in a separate process"
>and that's exactly what it does.

Yes, i have read the docs. If i start it with
$konsole
it opens a new process/window and blocks the calling process. If I use
$konsole --separate
it opens a new process/window and blocks the calling process. So, what is the
difference?

>--new-tab will open a new window if konsole isn't set to run all windows in a single process (Settings -> >Configure Konsole -> General).

Cannot confirm. It only works if the current Konsole was started with
"--new-tab". Otherwise the flag is ignored and a new window is opened. The
setting "Run all Konsole windows in a single process" does not change anything.

My problem is this test case: A Konsole window was started with "konsole". Now
all three commands
"konsole"
"konsole --separate"
"konsole --new-tab"
show the very same behaviour.

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


More information about the konsole-devel mailing list