By default when started from a terminal, Konsole will run in the background. Use
--noforkto force Konsole to run in the foreground.
This is needed for some scripts and commands to work as expected:
konsole --nofork -e sleep 3 ; echo 1
kdesu -u kdeuser konsole --nofork
Some fonts might be unavailable for usage in Konsole, although they are available in other applications. That doesn't mean there is a bug in Konsole. Konsole requires monospaced fonts to provide the best visual result, so it asks Qt™ to only list monospaced fonts.
If you are sure a font is really monospaced but unavailable in Konsole, then please report the problem to Qt™.
Since KDE4 all the tabs use the same process ID. This has the side-effect that if one tab's process has issues, all the other tabs may experience issues as well.
This is most noticeable when a command that connects to an external device or system (ssh, nfs) has issues.
Konsole treats arguments after the
-eoption as one command and runs it directly, instead of parsing it and possibly dividing it into sub-commands for execution. This is different from xterm.
konsole -e "command1 ; command2" does not work
konsole -e $SHELL -c "command1 ; command2" works
Konsole doesn't provide convenience for running login shell, because developers don't like the idea of running login shell in a terminal emulator.
Of course, users still can run login shell in Konsole if they really need to. Edit the profile in use and modify its command to the form of starting a login shell explicitly, such as "bash -l" and "zsh -l".
--new-taboption sometimes behaves strangely. It may create new window, or it may create new tab in another existing Konsole window instead of the current Konsole window.
Those behaviors feel strange, but they are not necessarily bugs. The
--new-taboption tries to reuse existing Konsole windows, but not all Konsole windows are reusable. All Konsole windows opened through KRunner are reusable, while most Konsole windows opened from command line are not.