Core LibraryalphaTopics

Choose documentation 3

latest

Current version

latest
English

Prerelease This site documents an alpha of libtmux. Its structure, URLs and APIs are subject to change.

Edit this page on GitHub

Errors and exceptions

A command can fail because tmux rejects it, or because the transport stops before returning a reply. Inspect the reported error and delivery state before retrying a mutation: tmux may already have received it.

For lookup failures caused by zero or multiple matches, see Filtering and queries.

A failed command, as a value

TmuxCommandError reports a command tmux rejected. TmuxTransportError reports a failure to obtain a reply. Catch these error types separately when the distinction affects recovery.

Distinguish a command rejected by tmux from a transport failure:

import { TmuxCommandError, TmuxTransportError } from "libtmux";
try {
await pane.capture();
} catch (error) {
if (error instanceof TmuxCommandError) {
error.args; // the argument vector
error.exitCode;
error.stderr; // tmux's own lines
} else if (error instanceof TmuxTransportError) {
error.kind; // "cancelled" | "pipe" | "protocol" | "spawn" | "timeout"
error.delivery; // see below: this is the question a retry depends on
}
}

Is it safe to retry?

Retry a mutation automatically only when you know it was not dispatched, or when repeating it is safe for your operation. A timeout, cancellation, or dropped connection can occur after tmux has acted. These APIs expose delivery information:

TmuxTransportError.delivery distinguishes not_started, written, replied, and indeterminate. Only not_started establishes that retrying cannot repeat an already-dispatched command.

import { TmuxTransportError } from "libtmux";
try {
await session.newWindow({ name: "build" });
} catch (error) {
if (error instanceof TmuxTransportError && error.delivery === "not_started") {
// safe to retry: nothing reached tmux
}
}

Treat unknown delivery as potentially executed.

A not_started result means the request did not reach tmux. A written result means the transport accepted the request but no terminal reply arrived.

For subprocess calls that complete normally, inspect the exit status. If a call is interrupted or times out without a delivery state, check tmux’s resulting state before repeating a mutation.

Esc

Type to search.

Reference preview Open reference