an opinionated terminal multiplexer in C with programmable pane chrome https://git.sl0p.foo/slosh.git/atom/?h=v0.1.4 2026-09-02T13:47:10Z 2026-09-02T13:47:10Z user user@clank 2026-09-02T13:47:10Z urn:sha1:975a8933685a058147a2fc2546ecddc74a6f2d91 2026-09-02T13:45:32Z user user@clank 2026-09-02T13:45:32Z urn:sha1:311979f10132697b990a670c6c99b19c1c33d623 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. 2026-09-02T13:38:38Z user user@clank 2026-09-02T13:38:38Z urn:sha1:8c1553801a9812bf4e8541872eb720470ce89a0b Vendoring by pinned commit stays (D12) -- the package channels build from source archives where submodules are empty, the arch build is offline-clean because the core is in the tarball, and upstream has no stable release channel to depend on anyway. What was missing is the watching: vendor-check reads the pin from vendor.json, asks the GitHub API what happened since, and lists the commits touching the terminal core. First run found 120 relevant commits in three weeks, including upstream fixing the same class of kitty-graphics bug our patch 0001 fixes -- which is the argument for finally sending it. 2026-09-02T13:26:52Z user user@clank 2026-09-02T13:26:52Z urn:sha1:5dfb761d3060bff5be8623272fdaf0eeb27706ca ship calls arch-repo without the ZIG= prefix the by-hand runs had, so the leg died on makepkg's dependency check mid-release. arch-repo now derives ZIG from PATH when pacman has no zig, and exports it. The formula and PKGBUILD pins ride along: ship's steps 6 and 7 had already written them when the leg failed, and its preflight rightly refuses a dirty tree. 2026-09-02T13:23:48Z user user@clank 2026-09-02T13:23:48Z urn:sha1:e0e54c44ed59ccab41e2dfb0df40c87f0611011f 2026-09-02T13:21:52Z user user@clank 2026-09-02T13:21:52Z urn:sha1:670add69317750ebc62f92662ea55d2e42439334 Stamped by build-site from ./VERSION, which the release invariant keeps equal to the newest tag -- so the page cannot advertise a version that was never cut, and nothing is bumped by hand. 2026-09-02T13:20:50Z user user@clank 2026-09-02T13:20:50Z urn:sha1:aea3e11f4cfa233db008076365e08a401c0e02a1 2026-09-02T13:19:28Z user user@clank 2026-09-02T13:19:28Z urn:sha1:578f2fe4901fbb82ea93fe2125598327dfc9bb14 The multiplayer patch proved the repo takes patches; say so where people can see it, and give the not-yet-an-issue conversations somewhere to happen. 2026-09-02T13:17:19Z user user@clank 2026-09-02T13:17:19Z urn:sha1:e468637d7d01a3a3bcfff24b0ce641e1fa8997df 2026-09-02T13:17:01Z user user@clank 2026-09-02T13:17:01Z urn:sha1:bce260f8f2b63c4e99d416ba483ff7d14b4bb1de Parentheses for the asides, colons for the explanations, commas and semicolons for the joins, (none) for the empty table cells. Same treatment the landing page got, across README, docs/, and both manpages (\(em included).