aboutsummaryrefslogtreecommitdiffstats
path: root/vendor/libghostty-vt/src/build/docker (follow)
Commit message (Collapse)AuthorAge
* vendor: libghostty-vt bedb6f2 -> 3c1ef5b3 (2026-09-01)user2026-09-02
| | | | | | | | | | | | | | | | | Three weeks of upstream: 504 commits, 120 touching the terminal core -- OSC 5522, kitty relative placements, C0 fixes, the wuffs pixel path. Rebuilt from ghostty's own dist step (zig build dist -Demit-lib-vt=true), zig floor unchanged at 0.16.0, and slosh's C usage compiled unmodified. Patch 0001 is re-implemented, not retired: upstream rewrote the area into ImageStorage.clearScreen but kept the behaviour we patch out -- a terminal clear still reclaims transmitted-but-unplaced images, which breaks the upload-once place-per-frame pattern the protocol's two verbs exist for. The patch now removes just that sweep; the placement clearing and orphan reaping stay upstream's. Their recent 'preserve data on unmatched delete' fixes the same class of bug, so sending ours upstream remains the way to actually retire it.
* vendor: an unanchored build/ ignore was eating libghostty-vt's build toolinguser2026-08-24
The build/ pattern matched every directory of that name, not just our build output at the root -- so vendor/libghostty-vt/src/build/ (the library's own build.zig helpers) never made it into git, and make vendor broke on fresh clones. Anchor the ignore to /build/ and restore the 284 files it had silently dropped.