← Back to collection

Windows Within Windows: Emacs, Zellij, and Why I Returned to tmux

After exploring Emacs, Zellij, and tmux, I returned to tmux for a practical reason: its relationship with iTerm2 and the rest of my Mac.

I have spent enough time inside terminals to appreciate a peculiar problem: eventually, the terminal becomes a desktop of its own. There are shells, editors, logs, remote machines, and experiments running at once. The question stops being which terminal should I open? and becomes how do I keep my working context intact?

I have used Emacs for years, learned to navigate with Vim keybindings, and experimented with both Zellij and tmux. All three can organize work, but they are not interchangeable. What I wanted was not the cleverest layout. I wanted to move between tasks without having to think about the window manager.

Three approaches to the same problem

Emacs approaches windowing from inside the editor. Buffers are not files, windows are views onto buffers, and frames can act as separate application windows. That is powerful when editing, documentation, and interactive shells are part of one Emacs-centered environment. I still appreciate how much work it can hold together, especially in its native macOS GUI.

Zellij approaches the problem as a modern terminal workspace. Discoverable keybindings, layouts, floating panes, and session management make it welcoming. I liked being able to see what was happening without memorizing every command first. For a while, it felt like the natural next step.

tmux is less concerned with being discoverable. It is a long-established terminal multiplexer built around sessions, windows, and panes. It can be terse, but that simplicity becomes an advantage once the keybindings are familiar. Sessions persist independently of a particular terminal client, making tmux particularly useful on remote hosts. That persistence matters more to me than decorative pane layouts.

What matters to meEmacsZellijtmux
Center of gravityEditor and buffersTerminal workspacePersistent terminal sessions
Learning experienceDeep, customizableFriendly, discoverableSpare, keyboard-driven
Remote workVia Emacs tools / shellsWorks in terminalsExcellent fit for SSH sessions
macOS GUI integrationNative Emacs GUITerminal-hosted interfaceiTerm2 tmux integration

This is a comparison of how they fit my work, not a universal ranking.

Why I returned to tmux

The deciding factor was iTerm2’s tmux integration. With tmux control mode, iTerm2 can present tmux windows and panes as native iTerm2 windows and split panes. That matters on a Mac where I already value native window management and keyboard navigation.

There is an important technical distinction: tmux does not magically add graphics support. iTerm2’s image and terminal features, the terminal protocol in use, and the application rendering the output all influence what can be displayed. My preference is for the integration experience—not a claim that tmux itself renders graphics better than Zellij.

For example, I can attach a tmux session through iTerm2’s integration:

# Run inside iTerm2, with tmux installed
tmux -CC new -A -s work

And when I connect to a remote server from an ordinary terminal, the same tmux vocabulary still works:

ssh devbox
tmux new -A -s investigation

The first workflow depends on iTerm2’s control-mode support; the second is ordinary tmux. That portability is part of the appeal. I do not need a separate philosophy for local and remote sessions.

A working day, not a dashboard

One pane might hold a Rust service, another its logs, and a third an HTTP request or a test run. I can leave a long-running task in one pane while inspecting its output in another, without rebuilding the workspace each time. When an interruption arrives, I switch sessions rather than rearrange the entire desktop. The session holds the context until I return.

I am not trying to fit every application into a grid of panes. Emacs still has a place. Zellij remains an interesting alternative. But tmux gives me a small, dependable layer between my shell and my terminal application, and iTerm2 makes that layer feel natural on macOS.

The next question is more mundane—and arguably more important: once I have a good workspace, how do I find and open things quickly? That is where Yazi became my primary terminal file manager.