Learn Tmux - Pre-Requisites Skill & Setup Environment

#Introduction

Welcome to the Learn Tmux series! This series will take you from zero to production-ready with tmux, across 28 episodes in total: starting from prerequisites & environment setup, history & client-server architecture, session/window/pane lifecycle, prefix key & keybindings, copy mode & clipboard, ~/.tmux.conf configuration, pane layouts, multi-session workflow, status bar & themes, format strings & variables, custom keybindings & command mode, options & environment, persistence & session restore, scripting & CLI automation, hooks, TPM plugin ecosystem, remote development & SSH, multi-server & shared sessions, security & hardening, nested tmux, popups & latest features, and finally a production-ready setup.

Before you press any key, first understand where tmux sits in the stack. tmux is not a terminal replacement — it runs on top of the terminal, usually inside a shell. You open a terminal, enter tmux, and everything you see on screen is the output of the processes living inside it. Every tmux pane maps to a PTY (pseudo-terminal), where a shell process runs. When you detach, tmux releases the client from the server, but the processes inside the panes keep running because they never receive SIGHUP. This is why tmux sessions survive a dropped SSH connection — and it is the main reason this series exists.

Episode 0 is your roadmap: the fundamental skills you must have, the software we set up (tmux 3.7b, a modern terminal, a Nerd Font, supporting tooling), and verification that everything works.

#Fundamental Skills You Must Have

tmux is a container for processes, and most of the processes you run deal with files and services. Without the following skills, even the most sophisticated tooling setup will be useless.

#Navigation & File Management

You should be comfortable changing directories, listing contents, and creating, copying, moving, and deleting files:

ls -la
cd ~/proyek
mkdir -p ~/lab/tmux
cp config.tmux backup.config.tmux

Add mv to move or rename files, and rm to delete — skills you will use every day, including when managing tmux configuration files in episode 8.

#Job Control in the Shell

Before multiplexers became popular, developers relied on shell job control to run several things in one terminal — a clunky trick that was easy to get tangled up in. Understand the following inputs:

Job control matters for two reasons: first, understanding how processes live and die in a terminal makes it easier to grasp tmux's detach concept; second, job control is still useful inside a pane.

#SSH & Remote Server Basics

Most real-world tmux usage happens over SSH, managing production servers. Remember this rule: SSH is a remote terminal session. When the connection drops, the remote terminal closes and every process inside it receives SIGHUP — unless that process is protected by tmux.

ssh devnull@203.0.113.42
ssh -i ~/.ssh/deploy-key devnull@203.0.113.42

For long sessions on unstable networks, the following ~/.ssh/config configuration makes the connection much more resilient:

Host server-prod
    HostName 203.0.113.42
    User devnull
    ControlMaster auto
    ControlPath ~/.ssh/cm-%r@%h:%p
    ServerAliveInterval 30
    ServerAliveCountMax 3

ControlMaster auto enables connection multiplexing (a second connection does not need to re-handshake), ServerAliveInterval 30 sends a keepalive packet every 30 seconds, and ServerAliveCountMax 3 closes the connection after three failed keepalives. You do not need to memorize these flags — what matters is understanding the concept: a stable connection is the best prerequisite for working with tmux remotely.

#Environment Variables & Shell Config

tmux inherits its environment from the shell that launches it. You should understand $PATH, $HOME, and where your shell configuration lives (~/.bashrc or ~/.zshrc), because in episode 8 we will add a line to load the tmux configuration from an external file.

echo $PATH
echo $HOME

#Software You Need to Set Up

#Installing Tmux 3.7b

The version we use throughout this series is tmux 3.7b — the latest stable release. Some of the features we cover (popups, floating panes, line selection in copy mode) are only available in version 3.5 and above, so make sure your version is correct.

#Linux

Ubuntu/Debian (apt)Fedora/RHEL (dnf)Arch (pacman)

sudo apt update && sudo apt install -y tmux

sudo dnf install -y tmux

sudo pacman -S tmux

#macOS

brew update
brew install tmux

#Build from Source

If the distro package is too old, build from source using a specific version tag:

sudo apt install -y libevent-dev libncurses-dev build-essential
git clone --depth 1 --branch 3.7b https://github.com/tmux/tmux.git
cd tmux
sh autogen.sh
./configure && make
sudo make install

#Verifying the Installation

Once installed, verify the version — the output should show tmux 3.7b (or at least 3.7.x):

tmux -V

#A Modern Terminal with True Color

tmux renders a screen cell grid on top of your terminal, so the display quality depends on the terminal you use. A modern terminal with true color (24-bit) will render the status bar theme smoothly; an older terminal that only supports 256 colors makes colors look washed out.

#Installing a Nerd Font

A Nerd Font is a font patched with thousands of glyphs/icons that a modern status bar needs — for example triangles, folders, and git symbols. Without a Nerd Font, those icons show up as empty boxes (tofu).

Recommendations: FiraCode Nerd Font or JetBrainsMono Nerd Font.

Install JetBrainsMono Nerd Font

mkdir -p ~/.local/share/fonts
wget https://github.com/ryanoasis/nerd-fonts/releases/download/v3.2.1/JetBrainsMono.zip
unzip JetBrainsMono.zip -d ~/.local/share/fonts
fc-cache -fv ~/.local/share/fonts

#Supporting Tooling

Install tooling (Ubuntu/Debian)

sudo apt install -y git fzf build-essential

#First Verification: Running Tmux

Once everything is ready, it is time for your first test:

tmux
tmux new -s lab

You will enter a tmux session with one window containing a single pane — the usual shell prompt, but now with a status bar at the bottom. To prove tmux is alive:

1. Press Ctrl+B then ? — the keybinding list appears. Press q to close it.
2. Press Ctrl+B then d — you detach back to the normal shell prompt. The processes inside tmux keep running.
3. Return with tmux attach -t lab.

#Common Pitfalls

1. tmux version too old. Stable distro repositories often ship 3.2-3.4, so the new features (popups 3.5, scrollbars 3.6, floating panes 3.7) are missing. Solution: build from source with the 3.7b tag, or use a community repository.
2. The terminal does not support true color. Status bar colors look washed out or wrong. Solution: use a modern terminal (Kitty, WezTerm, Ghostty, Alacritty, iTerm2, Windows Terminal).
3. The Nerd Font is not set in the terminal. Status bar icons appear as empty boxes. Solution: install a Nerd Font, change the font in your terminal settings, then restart the terminal.
4. command not found: tmux. The binary is missing from $PATH. Solution: check the install location, add it to your shell config (~/.bashrc/~/.zshrc), then open a new terminal.
5. SSH keeps dropping while working remotely. Solution: enable ServerAliveInterval and ServerAliveCountMax in ~/.ssh/config, and protect your work with tmux so nothing is lost when the connection drops.
6. Pressing exit in the last pane. Closing all panes/windows closes the session and kills the processes. If you want to come back later, use detach (Ctrl+B then d) — not exit.

#Conclusion

In this episode 0 we built a solid foundation: we mastered the fundamental skills (CLI navigation, job control, SSH, and environment variables), installed tmux 3.7b, set up a modern terminal with true color, installed a Nerd Font, and added the supporting tooling (git, fzf). We also verified that the first session runs and that the Ctrl+B prefix responds.

Key takeaways to carry with you:

• tmux runs on top of the terminal; every pane is a process inside a PTY.
• Detach ≠ close — detaching releases the client, it does not kill the session.
• Make sure tmux 3.7b, a true color terminal, and a Nerd Font are properly installed.
• Master the CLI, job control, and SSH basics — you will use all of them inside panes later.
• The most common mistakes are an old version, a wrong font, and a wrong PATH — check all three first when something goes wrong.

Make sure all of the tools above are ready, because the next episode covers concepts. In episode 1 next, we will discuss the history, background, and why the world needed tmux — from the problems before modern multiplexers, GNU Screen (1987), the birth of tmux by Nicholas Marriott (2007), to the version 3.x roadmap that brought modern features. Stay excited — the tmux learning journey is just beginning!