I love screen, and I love it even more when it’s patched to split vertically too. But screen isn’t the only game in town, if you like life at the command line. You might remember a long time ago, my rather brief infatuation with dvtm, which dissipated quickly when I realized that screen ran much lighter and faster on ancient hardware.
On the other hand, there is also tmux, which does a lot of things that screen should, but doesn’t really.
Not a particularly stellar screenshot there, but it illustrates the point. Just a quick look at the man page will show you a few things tmux does that screen might not. Preset pane arrangements, a highlight for the active frame, and a few other things all stand out at the start. The command sequence will take a little getting used to, and of course the default keybindings are a little different, but the same ideas are there and I doubt it would take long to adjust.
The real benefit to tmux, if it can be called a “benefit,” is that it is actively developed, with the most recent update in March. It’s certainly no requirement for admission to my system, but I do like to think that the folks who build a program are still interested in their project and pursue its future. Not required, but I get a warm, fuzzy feeling from that.
As far as software “weight,” I don’t see much that differs between tmux and screen when I look at them side-by-side in htop. I’ll do a little more profiling though, and see if there is a winner. One of the nice things about an extremely slow machine like this one, is that I can better see small increments in processor demand, while faster machines would be harder to read. Probably.
I will probably try to spend more time in tmux over the next few days, and see if it will usurp screen. It’ll give me a twinge of disloyalty, but that always happens when I find a new toy. …
P.S.: And yes, there is still dtach to consider. Sigh, so many programs, so little time. …