diff options
| author | user <user@clank> | 2026-08-11 14:14:53 +0200 |
|---|---|---|
| committer | user <user@clank> | 2026-08-11 14:14:53 +0200 |
| commit | 9441f1b177c1e08f4ceae76ef70d444103d15efa (patch) | |
| tree | bf59f9655fc32e46cd3f6c15e599f5b6dbc10281 /zellij-integration-tests/tests/snapshots/resize__resize_decrease_down.snap | |
| parent | sl0p: add `arrangement` to build a tree for N panes (diff) | |
| download | sl0ppij-9441f1b177c1e08f4ceae76ef70d444103d15efa.tar.gz sl0ppij-9441f1b177c1e08f4ceae76ef70d444103d15efa.tar.xz sl0ppij-9441f1b177c1e08f4ceae76ef70d444103d15efa.zip | |
sl0p: cap how many rows the stacked-pane picker takes
A stack reserves one row per member plus a padding row, so a deep stack spends
most of the screen listing itself. `stack_list_max_rows` caps that; the list
windows around the focused member and reports the rest as "+N more".
The indicator goes in the padding row the list already reserves, so it costs
no extra row and never displaces a real entry. Entries keep their real rank
rather than renumbering from 1, otherwise the numbering stops meaning anything
once the window has scrolled. The window slides on ordinary focus movement,
which is also why this needs no new keybinding -- Action is a protobuf enum
and the prost assets cannot be regenerated here (no protoc).
A fixed cap rather than hover-to-expand on purpose: reserved_top_rows feeds
pane geometry, so growing the list on hover would resize the pane's PTY and
reflow whatever is running in it on every mouse move. A real expand/collapse
has to be an overlay that reserves nothing, which is a much larger change to
the render path.
reserved_top_rows and the renderer both go through stack_list_window(); if
they disagreed the list would draw into rows the geometry never reserved, i.e.
over the pane beneath it.
Diffstat (limited to 'zellij-integration-tests/tests/snapshots/resize__resize_decrease_down.snap')
0 files changed, 0 insertions, 0 deletions
