# error.ControlModeErrorKind

- **Module:** error
- **Package:** libtmux
- **Language:** Rust
- **Kind:** enum
- **Source:** https://github.com/libtmux/libtmux-rs/blob/f0e37052c232636b61d095817046e6bfc8f2ca40/crates/libtmux/src/error.rs#L114
- **Page:** https://libtmux.org/en/rs/latest/reference/error-controlmodeerrorkind/

Why a control-mode connection failed.

The distinction matters to a caller: a connection that never opened is a
setup problem, whereas one that closed mid-command may simply mean the
session it was attached to has ended.

## Members

- `Transport` (constant): The live control connection could not read from or write to its pipes.
- `MissingPipes` (constant): tmux started without giving the crate the pipes it asked for.
- `Closed` (constant): The connection closed before the command was answered.
- `DispatchTimedOut` (constant): A command's deadline elapsed before it was committed for writing.
- `TimedOut` (constant): The attach opening or a committed command exceeded its deadline.
- `Unread` (constant): The caller stopped reading events, so the connection could not reach this command's reply.
- `UnrepresentableCommand` (constant): The command contains an argument no control-mode line can carry.
- `InvalidSubscriptionName` (constant): A subscription name was empty, or contained a colon.
- `BlockingCommand` (constant): The command would hold the connection's one command queue.