summaryrefslogtreecommitdiff
path: root/test/record_casts.py
Commit message (Collapse)AuthorAge
* rename: the terminal frontend is the tui (-Dplatform=tui, src/tui/tui.zig, ↵Gabriel Schneider14 days
| | | | | | | --tui with --tty kept as its old spelling, the process tests' backend .tui and --backend=tui, docs/typ/builtins-tui.json, the Settings report's platform), and the builtin Tty is Term (its registry entry, SPC n t, every default tag, the docs, tests and snap scripts), Tty still run as Term through exec.acme_words, Tty+fish too on a tag and a ctl; tty as a pane's raw mode and as the OS's terminal unchanged Co-Authored-By: Claude Opus 5.5 <[email protected]> Claude-Session: https://claude.ai/code/session_016Y9MNAtZenFv4weoMD3cge
* The terminal casts pin the orchard theme and show all four syntax colours, ↵Gabriel Schneider2026-10-01
| | | | | | | | | | | | and the petscii cast opens its pictures on camera from a README pardes colours four syntax classes (keyword, string, number, comment), so main.c gains a comment to show the fourth; types and function names stay plain in any theme. The petscii cast starts on a README naming the pictures and the manual, right-clicks each open, no longer runs Petscii, and searches 'bit 21', which first appears on the CPUID page. Co-Authored-By: Claude Opus 5.5 <[email protected]>
* The landing's terminal casts are recorded: live text, terminals as panes, ↵Gabriel Schneider2026-10-01
and images and PDFs in a plain terminal, each a tty pardes that test/record_casts.py drives in a pty of its own as a plain xterm The script answers only what an xterm answers, so images fall back to PETSCII glyph art and a PDF to its text layer. It stamps each scripted step on a virtual clock and writes the cells the step changed, as pyte saw them, so the same input makes the same file. The petscii cast generates its Mandelbrot views and reads the Intel SDM (--pdf) through a symlink. Co-Authored-By: Claude Opus 5.5 <[email protected]>