I need some clarifications about these arguments: What does `--separate` actually do? It does not fork the process, it always blocks the parent. And it always starts a new instance/window. Is this a bug or does it something else? And `--new-tab` opens a new window in some cases: 1. Start an instance with "$ konsole" 2. Try to open a new tab in this instance: "$ konsole --new-tab": a new window is opened If the initial instance is started with "konsole --new-tab" it works as expected. Another bug? Reproducible: Always
From `konsole --help`: "--separate, --nofork Run in a separate process" and that's exactly what it does. --new-tab will open a new window if konsole isn't set to run all windows in a single process (Settings -> Configure Konsole -> General).
>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.
See bug#373440
Alex can you please confirm if this is the same as bug 373440?
Dear Bug Submitter, This bug has been in NEEDSINFO status with no change for at least 15 days. Please provide the requested information as soon as possible and set the bug status as REPORTED. Due to regular bug tracker maintenance, if the bug is still in NEEDSINFO status with no change in 30 days the bug will be closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging If you have already provided the requested information, please mark the bug as REPORTED so that the KDE team knows that the bug is ready to be confirmed. Thank you for helping us make KDE software even better for everyone!
This bug has been in NEEDSINFO status with no change for at least 30 days. The bug is now closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging Thank you for helping us make KDE software even better for everyone!