From b4c87360d3490ed681c760a444272ff08ed3180e Mon Sep 17 00:00:00 2001 From: Codeman maintainer Date: Tue, 13 Oct 2026 17:48:21 +0200 Subject: [PATCH] docs(api): paneHistoryLines is absent when the pane geometry was not read (#583 merge-time fix) Co-Authored-By: Claude Opus 5.5 (1M context) --- docs/api-reference.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/docs/api-reference.md b/docs/api-reference.md index ee0ec3a0..da5efdd2 100644 --- a/docs/api-reference.md +++ b/docs/api-reference.md @@ -544,8 +544,8 @@ client that opens many concurrent waits against one session will still hit the c What a session's terminal shows, for a client to replay: `data.terminalBuffer`, with `source` (`mux-visible`, `mux-full-history` or `history`), `truncated`, `truncationReason`, `fullSize`, and `captureCols`/`captureRows` when the pane's -geometry was read. `paneHistoryLines` (present whenever the body is a pane capture) -is the number of scrollback rows tmux holds above the visible frame, which is the +geometry was read. `paneHistoryLines` (present when the body is a pane capture whose +geometry was read, like `captureCols`/`captureRows`) is the number of scrollback rows tmux holds above the visible frame, which is the most a `full=1` request can add. `truncated` describes the byte stream instead: for a pane with `paneHistoryLines: 0` (a fullscreen CLI in the alternate screen) the bytes a `tail` cut dropped are earlier repaints that no request returns. The capture runs