[Konsole-devel] [Bug 309249] New: konsole should add a "--separate" option for starting a new process
Jekyll Wu
adaptee at gmail.com
Tue Oct 30 11:33:10 UTC 2012
https://bugs.kde.org/show_bug.cgi?id=309249
Bug ID: 309249
Severity: wishlist
Version: 2.9.2
Priority: NOR
Assignee: konsole-devel at kde.org
Summary: konsole should add a "--separate" option for starting
a new process
Classification: Unclassified
OS: Linux
Reporter: adaptee at gmail.com
Hardware: Other
Status: NEW
Component: single-process
Product: konsole
Konsole uses class KUniqureApplication ever since KDE4. That decision means at
least two features:
1. All konsole instances started through krunner/menu/hotkey runs in the
same process
2. konsole instance started from one existing emulator/shell will run in
its own process, but runs in the background(more precisely, detached from the
existing emulator/shell).
That two features are sometimes annoying to users, and they need some way to
suppress that two features and make konsole behave in a more traditional way:
each instance runs in its own process, and runs in the foreground.
At the moment, the "--nofork" option (provided by KUniqureApplication) is used
for both purposes. I think using "--nofork" to suppress feature 1 is not a good
idea, because :
1. That is kind of abuse. That "--nofork" option is actually intended for
suppressing feature 2.
2. Its name is not easy to understand, and the option is hard to find
(buried in the output of --help-kde).
So I propose adding a new "--separate" option dedicated for suppressing feature
1. That doesn't means "--nofork" will not suppress feature 1 any more. It is
just that we should recommend using "--separeate" for that purpose.
Note, the "--separeate" option is inspired by roxterm. Actually, I remember
some user asked for that option in the #kde channel.
Reproducible: Always
--
You are receiving this mail because:
You are the assignee for the bug.
More information about the konsole-devel
mailing list