I was stupid. That "+[args]" is needed for the -e option. Without it,
konsole -e man ls will complains about "unexpected argument".
But that "+[args]" is actually a hack to make "konoele -e command args"
work. Konsole really doesn't support "konsole command args"
Need furthur investigation.
This reverts commit d556d110db.
Some NVIDIA users still require this option for Konsole to work as
expected
This reverts 66b4a96e93
Thanks to Matthias Kretz kretz@kde.org for patch/info.
BUG: 305307
FIXED-IN: 4.10
Since the menubar and tarbar settings are now global instead of per
profile , those cmdline options are useful to allow users to override
the defautl behavior.
The --hide-menubar and --hide-tabbar options can be used together
to simulate the miminal interface of xterm. I'm not sure whether
--show-menubar and --show-tabbar will be widely used , but add them at
the moment for the sake of completeness.
That option is broken for a long time (at least since KDE 4.6.2), yet
there is not a single bug report against it. That is a strong evince
that option is seldom used.
The ideal situation is whenever compositing is available, Konsole
supports translucent background out of box without user guidance.
One typical option is "--display", because two konsole windows
belonging to the same process are destined to be shown in the same
display, which defeats the purpose of the "--display" option
CCBUG: 297224
BUG: 179010
BUG: 297801
FIXED-IN: 4.9.0
REVIEW: 104653
The intention of using --nofork with Konsole is to start Konsole in
foreground and wait for it to finish, so the only logical behavior is
using new process instead of reusing existing process.
CCBUG: 288200
The old way of calling isatty() is problmatic, because the checked
file descriptor might be redirected by users. For example, 'konsole <
/dev/null > /dev/null 2> /dev/null' will make that method fail.
The better way is trying to open /dev/tty to see whether we have
controlling terminal.
Thanks to Askar Safin <safinaskar@mail.ru> for pointing this out.
It is possible that users invoke konsole from terminal in the form of
'konsole &> /dev/null' to get rid of warning messages. Checking stdout
won't give expected result.
On the other hand, 'konsole < ....' is almost never used. So checking
stdin should be more reliable.