So you like using Konsole eh? Sure, it is a great tool but it is enormously resource hungry. It is noticeable when you are actually using KDE, but if you decide to use it from somewhere else like your small and fast window manager it is almost totally unusable. If you feel the same way then read on.
Eterm/Escreen
Escreen is the King of Tabbing Terms in my opinion, it brings with it all the power of Eterm and GNU screen in one amazing little package.
Note
Escreen support may well work with other versions of screen, but I've only tested it personally with GNU screen and minscreen.
Note
Escreen is not a separate package, it is part of Eterm. It is possible you that don't have the Escreen support if you use binary packages, but this is a bug with the packager and distribution REPORT IT!! If you compile Eterm yourself be sure to read all the documentation including doc/README.Escreen.
There are some slight quirks with the Eterm usage though, so I definitely recommend reading the whole documentation in the Eterm package. But the simple truth is: if you already use screen then are going to love it.
There are a few unfortunate, in my opinion, side effects from the amalgamation of Eterm and screen. Some of your Eterm settings won't be carried over in Escreen sessions, but it is a simple job to add appropriate configuration information to your .screenrc.
mrxvt
If you currently use aterm or one of the hundred other rxvt variants then you can't go far wrong with mrxvt (formerly materm).
There are a lot of new features in mrxvt when compared to rxvt on top of tab support, including:
- Text shadowing
- Transparent menubars(although I find it a little unreadable personally)
- Run-time changing of the tinting options
- Pixmap styling for almost every background
- Support for the composite engine in current X.org builds(which I've never personally tested)
All things considered mrxvt is a great little package, especially for people, like me, who are used to rxvt or one of its derivatives.
Note
mrxvt makes a nice drop-in replacement for aterm too, if you disable the tabbar visibility(mrxvt.hideTabbar: true in your Xresources) it will look and feel almost exactly the same. This is obviously even more useful with the creeping dependence on afterstep that is happening to aterm in the 1.00 beta releases.