screen: The granddaddy of terminal multiplexers

I was for a very long time a faithful user of GNU screen.

2010-06-26-fmv-5120-vtclock

That has mellowed somewhat over the past few years, partly because tmux — I must admit — is leaps and bounds beyond what screen can do, but also just because there are other options too.

Things like dvtm, or even twin, which both handle the concept of multiple-terminals-one-screen in their own fashion.

Any of those three can do … somewhat something similar to what screen does, and have probably all seen more improvements over the years than screen.

I hold no one responsible for screen’s slow spiral into staleness; in fact, if anything, that makes screen quite easy to figure out: There is plenty of discussion about screen and how it works … even if some of it isn’t flattering. ๐Ÿ˜ฏ

It may be the ugly stepmother of terminal multiplexers, but you can’t deny that it does what it claims. And in the realm of console-based software, that alone is sometimes enough to get by. In my book, anyway. ๐Ÿ™„

Postscript, 2014-04-20: Wouldn’t you know it, only a day after whining about years without updates, this trickles down the pipe to my lowly Arch install.

2014-04-20-6m47421-new-screen

You could knock me over with a feather. ๐Ÿ˜ฏ Ask and ye shall receive, apparently. ๐Ÿ˜•

Advertisements

9 thoughts on “screen: The granddaddy of terminal multiplexers

  1. Pingback: Links 19/4/2014: | Techrights

  2. Pingback: scrollz: Fast, friendly and light | Inconsolation

  3. Pingback: splitvt: Under the most dire of circumstances | Inconsolation

  4. Pingback: neercs: Compiz at the console | Inconsolation

  5. Pingback: conspy: Take command of your command line | Inconsolation

  6. Pingback: whowatch: Don’t just take my word for it | Inconsolation

  7. Pingback: undistract-me: Quashing your ADHD | Inconsolation

  8. Pingback: undistract-me: Quashing your ADHD | Linux Admins

Comments are closed.