Terminal Multiplexers
A terminal window usually shows one shell at a time. That becomes cramped when one command is running a server, another is tailing logs, and a third is waiting for edits or inspections.
A terminal multiplexer such as tmux or screen puts another layer inside the terminal. That layer can split the screen into panes, keep sessions alive, and provide its own keyboard-driven copy mode.
The Boundary
There are two different programs involved:
| Layer | What it controls |
|---|---|
| Terminal emulator | Mouse selection, system clipboard shortcuts, font rendering, window integration. |
| Multiplexer | Panes, windows, sessions, copy mode, scrollback inside the multiplexer. |
This is why copying text can have more than one path. Selecting text with the terminal emulator is different from entering the multiplexer copy mode and selecting from its scrollback.
Common tmux Shape
In tmux, commands are usually introduced by a prefix key. The common default prefix is Ctrl-b.
Useful actions follow the pattern:
Ctrl-b [ enter copy mode
v start selection in vi-style copy mode
Enter finish selection
Ctrl-b % split pane horizontally into left and right panes
Ctrl-b " split pane vertically into top and bottom panes
The exact selection keys depend on the tmux mode and configuration. The durable model is to ask which layer owns the action: terminal selection or multiplexer copy mode.
Design Check
When a terminal workflow feels confusing, separate these questions:
- Am I selecting with the terminal emulator or inside the multiplexer?
- Is the key binding owned by tmux, screen, the shell, or the terminal app?
- Am I splitting the terminal window itself, or a multiplexer pane inside it?
That boundary keeps small keyboard recipes from turning into cargo-cult commands.