an opinionated terminal multiplexer in C with programmable pane chrome https://git.sl0p.foo/slosh.git/atom/web/recordings?h=docs-new 2026-08-30T15:03:55Z 2026-08-30T15:03:55Z user user@clank 2026-08-30T15:03:55Z urn:sha1:4e56615ea2119cfbe3042d578baff06d0fae6110 padding 1 2 was still in force when compact arrived, and the dense school reads best with the panes flush against its dividers. The cast now takes the padding back first -- cc rewrites the line to padding 0 on camera, one more save applying live -- so the compact beat lands on the layout it was designed around. 2026-08-30T15:01:45Z user user@clank 2026-08-30T15:01:45Z urn:sha1:1c63cb6aabb181a71ef56df75ccd7f4cd3a1d392 vim -u NONE kept the render machine's dotfiles out of the cast, but NONE also switches off filetype detection and syntax -- so the config demo was editing kdl in monochrome, underselling vim and the file both. The demo now authors its own six-line vimrc instead: syntax on, habamax (the webdemo's own look), shortmess for the column. The cast depends on vim's runtime and nothing personal, which is what NONE was protecting in the first place. 2026-08-30T14:58:43Z user user@clank 2026-08-30T14:58:43Z urn:sha1:f75bd436d03384642fab4176d36f74d410ece76d C-a e arrived as a strip along the bottom, and a 66-line config in a twelve-row strip reads like a keyhole. A quarter turn (C-a Space) right after it opens makes the editor a column with the height the file deserves -- and shows off the rotate while at it. The column brought back vim's hit-enter stall (the file-info message wraps at 49 columns), so the recording's EDITOR gains the same shortmess the webdemo's vimrc already carries. 2026-08-30T14:54:38Z user user@clank 2026-08-30T14:54:38Z urn:sha1:a1fd6a4e124c0b4e16c31ad6ef7ac5b6f617966d window.SLOSHCAST_SPEED, multiplied into each mount's own data-speed: the front page sets 1.25 and every recording plays a quarter faster than authored, the scripts under demos/ untouched -- their pacing is theirs, and how much of it a visitor's attention span gets is the page's call. The clock keeps counting cast-time, so the timestamps mean the same thing at any speed. 2026-08-30T14:51:59Z user user@clank 2026-08-30T14:51:59Z urn:sha1:c4140555d2d5b45afcc769f1ca182ab872a19a78 The title drag had one beat -- drop in the middle, trade places -- which undersells the feature: carried over a pane, the target subdivides into a centre and four edge bands, a band meaning "in beside it, on this side", filling the half it would hand over while every other candidate greys out. The cast now lingers over the centre, steers into a band, and drops -- and the drop restacks the whole tab, a rearrangement no swap could produce, chosen so the release visibly changes the layout (the first cut dropped a pane beside the neighbour it already had, and proved nothing). The band is aimed by its entry in the compositor's hit list, like every coordinate in these demos: the rect the program promised is the rect the pointer hits. The panes article's bullet follows suit. 2026-08-30T12:41:38Z user user@clank 2026-08-30T12:41:38Z urn:sha1:70e3320179b3388f18146d7dcbbd5242453862d3 C-a F drops a throwaway shell over a working layout; a monitor runs in it, moves with the keys that move boundaries, grows about its centre. Then C-a ?, the cheatsheet built from the bindings actually in force, and exit closes the float with the layout exactly as it was. The monitor is an htop impression with authored numbers, not htop: a recording that renders differently every run is a bug here, byte-for- byte is the contract. Phosphor, because every cast in the tour records under its own theme so the next step reads as a scene change. 2026-08-30T12:18:57Z user user@clank 2026-08-30T12:18:57Z urn:sha1:a4e1bb12760c2b9768e2917e41ac4600dcdf3156 2026-08-30T10:49:24Z user user@clank 2026-08-30T10:49:24Z urn:sha1:a3c5c69d089efd3d778e8b4ef859a6432cd3d07f