pardes.git - Pardes

	Commit message (Collapse)	Author	Age
*	Recipes work through a pane of their own, its look and exec, and keep a ↵	Gabriel Schneider	35 hours
\| \| \| \| \| \|	command pane while their open lasts; the docs give cmd panes, the err grep, alt-screen prompts, /pager's refusals, Tty+ on a ctl, --, and theme failures in words Co-Authored-By: Claude Opus 5.5 <[email protected]>
*	The docs say Grep is a literal search, that a write's own status comes ↵	Gabriel Schneider	36 hours
\| \| \| \| \| \|	before the log's last err, and that Delcol opens no +Unsaved Co-Authored-By: Claude Opus 5.5 <[email protected]>
*	The docs take round 32: petscii words in terminal and image tags, open ↵	Gabriel Schneider	37 hours
\| \| \| \| \| \|	records and EMFILE, ThemeFile failures and replays, trailing-colon looks, pty/run after clear, no-text addr refusals, held log reads at Restore, pardes - in one open, and a detached pty in pixels Co-Authored-By: Claude Opus 5.5 <[email protected]>
*	The docs take round 31: one +Pager per directory and how pardes - cleans its ↵	Gabriel Schneider	39 hours
\| \| \| \| \| \|	text, SYSTEMD_PAGER, a paged diff drawn as one, event reads in pieces, sel, write-back origins, +PdfSections rows, a PDF body by lines, bare :N looks and quoted bad values Co-Authored-By: Claude Opus 5.5 <[email protected]>
*	The docs describe the pager that landed: pardes - and its +Pager pane, a ↵	Gabriel Schneider	40 hours
\| \| \| \| \| \|	terminal's PAGER, command panes' cat, Pager pardes\|off, and pty/run no longer waiting in one Co-Authored-By: Claude Opus 5.5 <[email protected]>
*	Setting up your environment: a 9ns mount, pardes as the editor, pager and ↵	Gabriel Schneider	40 hours
\| \| \| \| \| \|	yazi opener, the shells with prompt marks, language servers, fonts and plan9port, each snippet tried Co-Authored-By: Claude Opus 5.5 <[email protected]>
*	The docs take the 9P agent's round 30: log stats 0, names escape every ↵	Gabriel Schneider	40 hours
\| \| \| \| \| \|	control byte, $winid and the pager defaults, the one client rule, and Shift-Esc said one way in the guide and the cheatsheet Co-Authored-By: Claude Opus 5.5 <[email protected]>
*	The book and the HTML hold every topic, and #doc links to its chapter or section	Gabriel Schneider	40 hours
\| \| \| \| \| \| \| \| \| \| \| \| \|	chapters now names guide, cheatsheet, scripting, reference, themes and building. #doc takes the chapter ids, keeps the old ones mapped onto them (tags and fs to the guide and the reference, config, keys and detached to their guide sections), and links in the book and the HTML, where a doc-links state says every chapter is there; on the A4 sheet it names the chapter and section. The reference points at the scripting and building chapters by #doc instead of in words, and the guide heading for pardes FILE and --wait keeps its two dashes. Co-Authored-By: Claude Opus 5.5 <[email protected]>
*	The guide walks a newcomer through pardes day to day, and the cheatsheet ↵	Gabriel Schneider	40 hours
	says what Esc and Shift-Esc really do Co-Authored-By: Claude Opus 5.5 <[email protected]>