diff options
| author | user <user@clank> | 2026-08-12 15:30:11 +0200 |
|---|---|---|
| committer | user <user@clank> | 2026-08-12 15:30:11 +0200 |
| commit | f9376a5ab8708c95d6ba40f069c9c29dedf67421 (patch) | |
| tree | 25124d44c0f54b0d5e4360fdd01ecfc8f1b70e30 /zellij-integration-tests/tests/snapshots/resize__resize_decrease_right.snap | |
| parent | sl0p: clickable action buttons in the pane status bar (diff) | |
| download | sl0ppij-f9376a5ab8708c95d6ba40f069c9c29dedf67421.tar.gz sl0ppij-f9376a5ab8708c95d6ba40f069c9c29dedf67421.tar.xz sl0ppij-f9376a5ab8708c95d6ba40f069c9c29dedf67421.zip | |
sl0p: document the pane status bar protocol
Reference for programs wanting to drive the bar: the OSC 5577 verbs, escaping
rules, click reports, limits, rendering behaviour, persistence, and the security
model.
Both worked examples were run against a real session rather than written from
memory, which caught four bugs in my own samples:
- the Python reader kept a trailing buffer window, so a processed report was
re-matched and every click fired twice
- it used tty.setraw, which also disables signals, leaving the sample unkillable
with Ctrl-C
- it exited via traceback and left the bar behind; both samples now clear it on
exit
- the shell reader echoed the report to the screen, and an `stty -echo` did not
help because bash's `read -n` saves and restores terminal settings around each
call. `read -s` is the fix.
Also verified and documented two behaviours I would otherwise have guessed at: a
BEL terminator works as well as ST, and the bar is not drawn when pane frames are
off (it lives in the frame row), reappearing when they return.
Diffstat (limited to 'zellij-integration-tests/tests/snapshots/resize__resize_decrease_right.snap')
0 files changed, 0 insertions, 0 deletions
