# control.ControlSender.mute_pane

- **Module:** control.ControlSender
- **Package:** libtmux
- **Language:** Rust
- **Kind:** method
- **Source:** https://github.com/libtmux/libtmux-rs/blob/8a648c0894dfffc9303583f753b6c8ae01f2fe76/crates/libtmux/src/control.rs#L750
- **Page:** https://libtmux.org/reference/rs/control-controlsender-mute_pane/

```
control.ControlSender.mute_pane(self, pane: &PaneId) -> Result<(), Error>
```

Stop tmux sending this connection what a pane writes.

A control client is sent the output of every pane in the session it
attached to, which is one window's worth or a hundred. One pane running
`yes` moves more than 20 MB in two seconds, and a client tmux judges
five minutes behind is disconnected with `too far behind`, so
discarding the unwanted panes on arrival is not enough.

Muting a pane that does not exist is not an error; tmux ignores an
unresolvable id here.

Below [`crate::since::CONTROL_PANE_OFF`] this pauses the pane rather
than taking it out of the stream, because taking it out crashes the
server. tmux reports a paused pane, so a caller reading
[`ControlEvents`] sees [`Event::Paused`] for it there and not on a
newer tmux. The pane stops arriving either way; what a paused pane
costs is the back-pressure, since tmux keeps draining its terminal.

# Errors

Returns an error when the connection has closed or tmux refuses the
stream change.