With this commit the option --nofork was removed. Nor in the announcement nor in the full apps 16.08.0 log this change is mentioned. https://quickgit.kde.org/?p=konsole.git&a=blobdiff&h=129a5cf0bc66ee4ddc7e30c1c5a2c94246277b3f&hp=5e1420e37363454cf5e7886a82381cb9eb4447d8&hb=27dec8d02f705c77eef45a2533bed203eec9454f&f=src%2Fmain.cpp the removal is desired? or it occurred by mistake? Reproducible: Always
I will add an example, this was a working line before the update of 16.08.0: konsole --nofork -e bash -c /tmp/.qt_temp_1508913749 where the .qt_temp_* file contains the instruction to be executed in the konsole.
Konsole never had a -c option AFAICT. In your example, -c is actually an option for bash. Konsole 16.08 (using QCommandLineParser) incorrectly treats it as an (unknown) option for konsole now though, instead of ignoring the arguments after -e and passing them to the command that is to be run (bash). See bug#366793. --nofork has indeed been "removed" in 16.08. I have no idea whether this is on purpose or by mistake, nor whether --nofork even still makes sense with KF5/Qt5. What I can say though is that this is also related to the switch to QCommandLineParser. The --nofork option was not konsole specific, but provided by kdelibs4's KCmdLineArgs.
I can confirm the removal. Really annoys me because I used this option every time I start an external editor in kmail.
Actually the --nofork option has been added to konsole yesterday: https://cgit.kde.org/konsole.git/commit/?id=c6ffcaff557760f46ba5813823868e656b45da0f So I think we can close this as fixed.