an opinionated terminal multiplexer in C with programmable pane chrome https://git.sl0p.foo/slosh.git/atom/contrib?h=v0.1.6 2026-09-02T14:57:12Z 2026-09-02T14:57:12Z user user@clank 2026-09-02T14:57:12Z urn:sha1:8aea65b9d9c0ed704a7171aa69ee2c615d818486 The docs header gains a right-aligned slosh.foo link (absolute, so a locally rendered build/docs points somewhere real too), and the README says the website exists, which it never did. 2026-09-02T14:40:32Z user user@clank 2026-09-02T14:40:32Z urn:sha1:abc2ee66fac8112c204e1f10df6741b4af25c416 optdepends says it at install time, the README and the install tab say it before. Our package deliberately does not ship the file: extra/ghostty-terminfo owns that path, and two packages must not. Without either, slosh's own ~/.terminfo copy covers it. pkgrel=2, both architectures rebuilt and republished. 2026-09-02T14:31:12Z user user@clank 2026-09-02T14:31:12Z urn:sha1:c534bee1dc7bb2c9929ca6a7e2d2af3fea17eaad 2026-09-02T14:22:03Z user user@clank 2026-09-02T14:22:03Z urn:sha1:f9986df0da09cc692e168e33ef9ccfab5b9d2faf The xterm-256color fallback works everywhere; the real entry is better, and a tarball user on a bare box had no easy way to get it. The entry is generated from the vendored tree (contrib/terminfo, so it describes the terminal core we actually ship), compiled with tic, embedded as bytes, and written to ~/.terminfo under every name it answers to, letter and Darwin-hashed layouts both. No root, no package, no conflict with a ghostty installed later. Proven end to end in a mount namespace: bare box falls back, installs, and the next pane says xterm-ghostty. 2026-09-02T14:10:48Z user user@clank 2026-09-02T14:10:48Z urn:sha1:9cc6ff911ac794c5831407358fddb7b7c9c24ef6 The v0.1.4 arch packages introduced themselves as 0.1.4-dirty: the tag's tarball has no .git, makepkg builds it inside the release box's repository, and git describe walked up and answered for the outer tree -- mid-release, when the paperwork is honestly dirty. Found at 0.1.2, diagnosed, and then left unfixed by yours truly. Two fences now. contrib/version only trusts a .git whose toplevel is its own root (helps every future tarball). The PKGBUILD exports GIT_CEILING_DIRECTORIES for build and package (helps regardless of which contrib/version the pinned tarball carries, which is why the first rebuild still said -dirty: the fix was outside the tarball). pkgrel=3; both architectures rebuilt, verified 'slosh 0.1.4', and republished. 2026-09-02T13:58:12Z user user@clank 2026-09-02T13:58:12Z urn:sha1:60d622062aefa1258e348c4085ab33e0e7e2ae48 Steps 6 and 7 rewrite the formula and PKGBUILD; building the site from the tag checkout with those uncommitted made git describe say -dirty, and v0.1.4's demo introduced itself as 0.1.4-dirty+webdemo. Commit the pins first, build the site from a clean tag second. 2026-09-02T13:57:00Z user user@clank 2026-09-02T13:57:00Z urn:sha1:0280bc0635cb02ff8a96be7f5d730fee9161c307 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:17:19Z user user@clank 2026-09-02T13:17:19Z urn:sha1:e468637d7d01a3a3bcfff24b0ce641e1fa8997df