an opinionated terminal multiplexer in C with programmable pane chrome https://git.sl0p.foo/slosh.git/atom/vendor/libghostty-vt.vendor.json?h=docs-new 2026-08-14T21:13:56Z 2026-08-14T21:13:56Z user user@clank 2026-08-14T21:13:56Z urn:sha1:d1442bc9550b00080c2f5671fa93eaad67fb0299 libghostty-vt's eraseDisplay called kitty_images.delete(.{ .all = true }) for ED 2 and ED 3, where the `true` also frees the image *data* of anything no longer placed. A full-screen program that clears and redraws therefore loses every image it uploaded, and every later placement of that id draws nothing. That breaks the half of the protocol worth having. Kitty separates transmitting an image (`a=t`, stored under an id) from placing it (`a=p`, put on screen) precisely so a program can upload once and place many times -- which is also why the delete command distinguishes `d=a` (placements) from `d=A` (placements and data). A screen clear should be the former. The patch removes only the freeing: placements on the cleared screen still go, and the image store still bounds itself with its 320MB limit and LRU eviction on insert -- the mechanism that makes keeping them safe, and that would be pointless if a clear dropped everything anyway. Found with a bouncing-DVD screensaver that uploads ten frames up front and places one per frame. It works in kitty; under us it drew nothing. D12 said "with a patches file if we ever need one". vendor/patches is that file, with the reasoning and what a re-vendor has to re-apply; the vendor json lists it. Worth sending upstream. 2026-08-13T20:00:03Z sl0p sl0p@sl0p.foo 2026-08-13T20:00:03Z urn:sha1:2c1b855c3cf8cf8841bf25cd939e478a7f0bfac8 Design contract in DESIGN.md. libghostty-vt vendored fresh from ghostty main@bedb6f2 (zig 0.16), built to a 14MB static lib. M0: pty spawn (no libutil), a lib-vt terminal per pane, a screen cell buffer, a diff emitter that repaints only what changed, raw mode, SIGWINCH, and a ~120Hz frame cap that coalesces pty reads. Also the seed of the headless harness: --headless dumps the composited screen without a tty, so composition is testable in milliseconds. tests/live_m0.py covers what headless cannot: raw mode, the diff emitter, resize propagation, and the quit path. 6/6 green.