error.ControlModeErrorKind
Rust
- Python Unavailable
- Ruby Unavailable
- Lua Unavailable
- TypeScript Unavailable
- Rust
- Go Unavailable
- Java Unavailable
- .NET Unavailable
- C++ Unavailable
- Swift Unavailable
- Module
- error
- Package
- libtmux
- Source
- crates/libtmux/src/error.rs
-
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.
Discussed in Errors and exceptions
9 declared, 0 inherited
Members
- DispatchTimedOut constant A command's deadline elapsed before it was committed for writing.
- BlockingCommand constant The command would hold the connection's one command queue.
- Closed constant The connection closed before the command was answered.
- InvalidSubscriptionName constant A subscription name was empty, or contained a colon.
- MissingPipes constant tmux started without giving the crate the pipes it asked for.
- TimedOut constant The attach opening or a committed command exceeded its deadline.
- Transport constant The live control connection could not read from or write to its pipes.
- 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.