GNU Screen 5.0 Released

Original Article ↗ Hacker News Discussion ↗

Scope of the 5.0 Release

  • Seen largely as a quality‑of‑life and bug‑fix release rather than a disruptive “major” change.
  • Notable new features discussed:
    • Truecolor support (called out multiple times as “finally” and a main reason some had moved to tmux earlier).
    • Session passwords, though some see this as security theater since you can’t attach to another user’s session anyway.
    • Fixes around Vim/Neovim needing double Esc due to mouse emulation.

Screen vs. tmux

  • Many long‑time Screen users migrated to tmux years ago for:
    • More flexible and scriptable window/pane splitting.
    • Easier, more readable configuration.
    • Strong plugin ecosystem and integrations (e.g., iTerm2 control mode).
  • Screen strengths:
    • Ubiquity on older/unmanaged systems and in tooling (e.g., used by some distro upgrade tools).
    • Lower resource usage reported by some.
    • Built‑in serial support (often used instead of Minicom for console access to routers/embedded boards).
  • One downside of tmux raised: it reuses the server’s environment across new sessions, potentially leaking env vars (including secrets) between shells; Screen does not.

Keybindings & Ergonomics

  • Large sub‑thread on prefix keys and conflicts:
    • ctrl‑a (Screen default, often used for tmux too) conflicts with Emacs/Bash “beginning of line” and can cause repetitive strain.
    • Users report remapping to ctrl‑b, ctrl‑j, ctrl‑space, ctrl‑t, ctrl‑o, ctrl‑], ctrl‑\ or even backtick; each option has its own trade‑offs with editor shortcuts and pasting behavior.
  • Nested sessions often drive people to keep different prefixes locally vs. remotely.

Use Cases & Workflows

  • Common patterns:
    • Persistent remote sessions to survive flaky SSH and keep long‑running jobs.
    • Using multiuser Screen sessions (screen -x) for pair‑debugging or training, with ACLs per window.
    • Running Emacs, vim, or other tools inside Screen/tmux, or conversely using Emacs/vim terminal features as the multiplexer instead.
  • Some now offload multiplexing to modern terminal emulators (e.g., WezTerm) or newer muxers (e.g., Zellij), citing better UX and discoverability, but still rely on Screen/tmux for long‑lived remote state.

Bugs, UX Issues, and Security Concerns

  • Complaints about Screen’s copy mode blocking the underlying process (bug referenced) and past issues with Esc handling.
  • Discussion of text‑based remote exploits against Screen and the difficulty of sandboxing such a tool, given its need to manage ttys and shells.
  • Nostalgic mentions of removed “nethack‑style” error messages and comparisons to similar “fun” features like sudo’s insults.