<feed xmlns='http://www.w3.org/2005/Atom'>
<title>pardes.git/test/perf-baseline-tui-fast.json, branch main</title>
<subtitle>Pardes</subtitle>
<id>https://git.0x4200.cafe/pardes.git/atom?h=main</id>
<link rel='self' href='https://git.0x4200.cafe/pardes.git/atom?h=main'/>
<link rel='alternate' type='text/html' href='https://git.0x4200.cafe/pardes.git/'/>
<updated>2026-11-09T06:30:49Z</updated>
<entry>
<title>idioms: the edit surface fails by name: the undo history (Journal.mark, Text.remember and step, File's, terminal's and edit's pushUndo and undoStep) returns error{OutOfMemory} instead of dropping an undo point, setEditText, enterInsert and insertTab return edit.Error with try where they reported each failure, Registers.put and setYank return error{OutOfMemory} instead of losing a yank, and their other-file callers decide (try under edit.Error, said on the pane by Undo, Redo, Pipe, Edit, Query, keys, look, completion, Incl and Plumb, ENOMEM or null where a 9P write answers, Ask's false); ctl.get and getFile return GetError (fs.ReadError, now named at fs.zig's surface, and InvalidName) for the *anyerror out-parameter and errno, the 9P get, Get and Edit's e mapping it as before; the OOM undo test pins the error; perf.zig's try relabels its harness hash, the three baselines re-keyed to it (their numbers the base's)</title>
<updated>2026-11-09T06:30:49Z</updated>
<author>
<name>Gabriel Schneider</name>
<email>gbrls@0x4200.cafe</email>
</author>
<published>2026-11-09T06:29:30Z</published>
<link rel='alternate' type='text/html' href='https://git.0x4200.cafe/pardes.git/commit/?id=84c8209d02f6830db861c3a8dde0c710c88075f0'/>
<id>urn:sha1:84c8209d02f6830db861c3a8dde0c710c88075f0</id>
<content type='text'>
Co-Authored-By: Claude Fable 5.1 &lt;noreply@anthropic.com&gt;
Claude-Session: https://claude.ai/code/session_016Y9MNAtZenFv4weoMD3cge
</content>
</entry>
<entry>
<title>perf.zig: --op &lt;label&gt; measures one gesture alone, and the three baselines (tui and gui Debug, tui ReleaseFast) are re-recorded on an idle machine at this head, re-keyed to the harness: the old files carried the pre-rewrite's numbers, and every cell is now the rewrite's own (render 90→81 µs Debug, 77→73 ReleaseFast; edits 2.6x, body-appends 100x faster)</title>
<updated>2026-11-07T05:20:27Z</updated>
<author>
<name>Gabriel Schneider</name>
<email>gbrls@0x4200.cafe</email>
</author>
<published>2026-11-07T04:20:25Z</published>
<link rel='alternate' type='text/html' href='https://git.0x4200.cafe/pardes.git/commit/?id=f2784acb88c98f33fed25dbf41f1a5af278c8e84'/>
<id>urn:sha1:f2784acb88c98f33fed25dbf41f1a5af278c8e84</id>
<content type='text'>
Co-Authored-By: Claude Fable 5.1 &lt;noreply@anthropic.com&gt;
Claude-Session: https://claude.ai/code/session_016Y9MNAtZenFv4weoMD3cge
</content>
</entry>
<entry>
<title>effects out, the theme crossfade: a theme change takes the chrome at once, as it always took the content; colors.ChromeAnimation (its OKLab steps, its retarget, the ticks and the frames it asked of nextWake) goes, Pardes.chrome is the theme's chrome, set as the theme changes, and the `animate` flag goes from loadThemeFile and applyThemeEffect with it, as does the build's -Dtheme-animation option (and its place in the wire's fingerprint); no frontend fades a theme of its own (a window crossfading every cell's colour for 160 ms is a copy of the last frame kept and blended, for one keystroke's change); the fade's tests go, the PDF test loses its ticks through a fade, and `core animation keeps wall time at 60, 120 and 144 Hz and across a stall` goes with the one animation that ran it; the perf baselines lose the option from their build identity; GUI goldens 16-debug and 17-terminal change, the golden session having faded its themes by default: a fade's frames kept the Debug word's announcement up in the picture's pane, which gave up a row to it under the Debug box; the tree before this change built with -Dtheme-animation=false draws exactly these frames, all sixteen byte for byte</title>
<updated>2026-11-05T18:23:49Z</updated>
<author>
<name>Gabriel Schneider</name>
<email>gbrls@0x4200.cafe</email>
</author>
<published>2026-11-05T16:28:13Z</published>
<link rel='alternate' type='text/html' href='https://git.0x4200.cafe/pardes.git/commit/?id=23c9932afe9bbf01aa84d780e9030dfb6e333475'/>
<id>urn:sha1:23c9932afe9bbf01aa84d780e9030dfb6e333475</id>
<content type='text'>
Co-Authored-By: Claude Opus 5.5 &lt;noreply@anthropic.com&gt;
Claude-Session: https://claude.ai/code/session_016Y9MNAtZenFv4weoMD3cge
</content>
</entry>
<entry>
<title>after the merge: the window's frame probe follows a Restore's new core (it pointed into the freed old one, so every frame after a Restore wrote freed memory); ov_pinch_scale and ov_touch_scroll_delta go (nothing wrote them once the pinch and touch_scroll events went; the Debug box loses its two dead rows, topbarexec and windowops regenerated alone and re-run); the perf baselines are named tui, as the frontend is (the perf gate had looked for perf-baseline-tui-*.json and found the tty-named files)</title>
<updated>2026-11-05T12:54:55Z</updated>
<author>
<name>Gabriel Schneider</name>
<email>gbrls@0x4200.cafe</email>
</author>
<published>2026-11-05T04:57:51Z</published>
<link rel='alternate' type='text/html' href='https://git.0x4200.cafe/pardes.git/commit/?id=534f7da02ac58e475bb24801d315d7b736bd9c38'/>
<id>urn:sha1:534f7da02ac58e475bb24801d315d7b736bd9c38</id>
<content type='text'>
Co-Authored-By: Claude Fable 5.1 &lt;noreply@anthropic.com&gt;
Claude-Session: https://claude.ai/code/session_016Y9MNAtZenFv4weoMD3cge
</content>
</entry>
</feed>
