https://bugs.kde.org/show_bug.cgi?id=366793
--- Comment #21 from Wolfgang Bauer <wba...@tmo.at> --- (In reply to Jonathan Marten from comment #20) > Some of > the required functionality can be restored by setting the parser to not > parse options after the first non-option argument: Yes, but this requires Qt 5.6 at least. Probably not a problem for KDE Applications 17.04, but it will prevent distributions that still use Qt 5.5 to backport the fix (I don't know if any of them ship konsole 16.08 though). > The workaround is to ensure that the first argument is not an option: Another workaround would be to make the '-e' option not take any arguments at all, then the actual command would be the first positional argument. (disadvantage: QCommandLineParser will not complain if there is no command at all after '-e', and the command itself may not start with a '-' but that can be ignored I suppose) Another way I see to fix the problem is to parse the command line manually before handing it over to QCommandLineParser, and strip off '-e' and all that follows (and handle it manually). Actually I experimented myself with both a bit already, but had no time yet to get it into a fully working shape... -- You are receiving this mail because: You are watching all bug changes.