Environment

Edit this page on GitHub

tmux uses the word “environment” for two genuinely different things, and a port’s API keeps them as separate as tmux does: the ordinary OS process environment tmux writes into every pane it spawns, and tmux’s own persistent variable store — set with set-environment, read with show-environment — that a new pane inherits but which lives in the server, not in any one process’s memory. The first is how code running inside a pane finds its way back to the server that launched it; the second is a small, scoped configuration surface, structurally the twin of the hooks tables in Options and hooks.

Locating yourself from inside a paneLink to section

tmux exports two variables into every pane it spawns: TMUX (<socket path>,<server pid>,<session id>) and TMUX_PANE (that pane’s own id, e.g. %1). Code that is running inside a pane — a script launched in a split, a hook, a test harness — reads them back to get a handle on itself, rather than searching the whole server for a pane it already is. Every port gives you some form of this, but they stop at different levels of the hierarchy:

Python, Go, and .NET give every level its own standalone call. Rust’s Session/Window/Pane::from_env take &Server as a parameter — you already need a Server handle before asking any of them where you are, where Python’s, Go’s, and .NET’s Pane-level call needs nothing but the environment. TypeScript verifiably has only Session.fromEnv(); no Pane, Window, or Server equivalent was found in its source.

A process not started inside a pane has nothing truthful to answer with, so every one of these raises rather than guessing: Python’s NotInsideTmux, Go’s FromEnvError, .NET’s TmuxObjectNotFoundException, and so on, each naming the missing or malformed variable rather than returning an empty or default object.

Java and C++ stop short of the paneLink to section

Neither port gives you a live object back the way the other five do, and they stop at different points:

• C++ has Server::from_env() and nothing past it — no verified Session, Window, or Pane::from_env() reading TMUX_PANE exists in the source for this page. Getting to your own pane means resolving TMUX_PANE yourself and looking it up through the server from_env() gave you.

• Java goes the other direction: TmuxEnvironment.current() parses both TMUX and TMUX_PANE fully, but hands back plain identifiers — a socket path, a server pid, a SessionId, an Optional<PaneId> — not a live Session or Pane. Resolving one of those ids into an object you can call methods on is a lookup you write yourself, shown in the class’s own Javadoc example:

Swift reads less than it couldLink to section

TmuxContext.current() parses $TMUX only — socket path, server pid, session id — and never reads TMUX_PANE at all, so it cannot name the pane or window a Swift process is running in, only the server and session:

Getting from there to the actual pane a script is running in is not covered by anything in TmuxContext — a real, verified gap rather than an overlooked accessor, since TMUX_PANE is simply never read.

tmux’s own environment variable storeLink to section

Separately from the OS process environment above, tmux keeps a persistent table of variables set with set-environment and read with show-environment — inherited by new panes tmux spawns, but not the same thing as any process’s actual environment at any given moment. Like hooks (Options and hooks), tmux keeps exactly two of these tables — global and per-session — and unlike hooks, no port even offers a window or pane scope to get wrong: there is no -w/-p flag for set-environment to begin with, so the trap that section describes for hooks has no equivalent here. Swift’s own doc comment states the contrast directly: “tmux keeps two, and only two: one global, and one per session… unlike OptionScope, whose four tables are all real.”

Python’s model is worth a specific note: set_environment writes a value, unset_environment (-u) removes it from the listing outright, and remove_environment (-r) is a third, different operation — it marks the name so new processes start without it, even if it was inherited from tmux’s own environment when the server started, while still listing it (as -NAME) rather than making it disappear. Swift keeps the same three-way split explicitly (setEnvironment, unsetEnvironment, removeEnvironment) with a doc comment spelling out exactly this distinction; TypeScript’s, Go’s, and Rust’s tables above show only set/read/unset because a -r-shaped remove wasn’t verified in their source for this page — treat its absence from those rows as unverified, not as confirmed missing.

Java and C++: no verified access to this table at allLink to section

Neither port’s main source exposes set-environment or show-environment under any name for this page. Both do let you seed a new pane, window, or session’s environment at spawn time — Java’s SessionSpec.Builder. environment(Map), WindowSpec.Builder.environment(Map), and SplitSpec.Builder.environment(Map) all set initial variables passed to new-session -e / new-window -e / split-window -e — but that is a one-shot value handed to a single spawning command, not a read/write handle on the persistent table show-environment reads back. If your program needs to read or change that table on an existing session in Java or C++, this page found no way to do it through either library.