zellij-org/zellij · error
cannot write to stdout
Error message
cannot write to stdout
What it means
Error "cannot write to stdout" thrown in zellij-org/zellij.
Source
Thrown at zellij-client/src/lib.rs:712
log::error!("Failed to send resize message: {}", e);
break;
}
}
crate::os_input_output::SignalEvent::Quit => {
break;
}
}
}
// Handle terminal messages
terminal_msg = connections.terminal_ws.next() => {
match terminal_msg {
Some(Ok(Message::Text(text))) => {
let mut stdout = os_input.get_stdout_writer();
if let Some(sync) = synchronised_output {
stdout
.write_all(sync.start_seq())
.expect("cannot write to stdout");
}
stdout
.write_all(text.as_bytes())
.expect("cannot write to stdout");
if let Some(sync) = synchronised_output {
stdout
.write_all(sync.end_seq())
.expect("cannot write to stdout");
}
stdout.flush().expect("could not flush");
}
Some(Ok(Message::Binary(data))) => {
let mut stdout = os_input.get_stdout_writer();
if let Some(sync) = synchronised_output {
stdout
.write_all(sync.start_seq())
.expect("cannot write to stdout");
}View on GitHub (pinned to e839bfffa5)
Solutions
- Ensure zellij runs attached to a real terminal with write access.
- Check the attached OS error for details (closed stdout, unsupported terminal).
When it happens
Trigger: Occurs at zellij-client/src/lib.rs:695 when the operation fails: "cannot write to stdout". Currently there is no defensive handling preventing or contextualizing this failure before it surfaces.
Common situations: Running under a non-tty, redirected stdout, or a terminal that disappeared.
AI-assisted analysis of zellij-org/zellij@e839bfffa5 (2026-08-19).
Data as JSON: /api/errors/e9c966ec57251e97.
Report an issue: GitHub.