Fairly recently Konsole was changed so that a new Konsole window does not show a single tab, it only shows tabs when there is more than one. I'm fine with this. However, I ran into a weird side-effect of this recently. I was clicking on one of my tabs (to open it) and accidently moved the mouse a little bit as I did this. As designed, the action of dragging a tab will detach the tab from the window into a new window. However, once the tab was detached in the new window, all I wanted to do was return it to the original Konsole window since it was an accident. Since the tabs don't show on a new window anymore, there was no way I could see to easily do this. I looked around in the menu a bit, tried dragging the window around and finally realized that I would have to open a new tab so that I could drag the accidentally detached tab back to my original Konsole window and then close the remaining newly-opened tab's window. Maybe this is just a rare corner case where we have to accept that there is no easy way do what we want (return the detached tab easily and intuitively), but maybe there is a reasonable way to allow for this?
FWIW, with this commit[1], dragging a tab should be less prone to accidentally detach it. This will be included in the 18.08 release. [1] https://cgit.kde.org/konsole.git/commit/?id=41b0b20a1946674d6b04c89b3b43f1a039196171
If the tab were harder to accidentally detach, that would probably be sufficient for me.
Jason, can you please confirm if this is still an issue with Konsole 20.08+.
It is.
It is still an issue in the sense that when a tab is detached there is no clear way to return it. However, since it is no longer easy to detach a tab (I can't do it by clicking and dragging the tab anymore), it is no longer easy to accidentally detach it and so this isn't a situation I find myself in often anymore.
Under the Konsole settings you can set the tab bar to be shown always. This way you always see the tab bar on any Konsole window and will always be available to drag the tab into another window.
This is a possible duplicate of Bug 403324.
Nah, that's different.