# error.Error.ClientSuspended

- **Module:** error.Error
- **Package:** libtmux
- **Language:** Rust
- **Kind:** constant
- **Source:** https://github.com/libtmux/libtmux-rs/blob/f0e37052c232636b61d095817046e6bfc8f2ca40/crates/libtmux/src/error.rs#L903
- **Page:** https://libtmux.org/en/rs/latest/reference/error-error-clientsuspended/

A client is stopped rather than gone, so listings leave it out.

Distinct from [`Self::ObjectGone`], and the distinction decides whether
to drop the handle: a suspended client is still on the server and is
listed again once it resumes, so the same handle keeps working.
[`Self::ObjectGone`] means it will not.

tmux omits a suspended client from `list-clients` while still resolving
it as a command target, which is what makes the two tellable apart. The
listing filters the dead, the exiting and the suspended together, so
absence from it does not say which of the three happened.

Both [`crate::Client::suspend`] and locking a client arrive here,
because tmux marks them with one flag. A client resumes when its
process continues -- the suspended one on `SIGCONT`, the locked one
when its `lock-command` exits.