From cfcff94ab2b1ff5a0fb61dead60ead09bf892d30 Mon Sep 17 00:00:00 2001 From: Gabriel Schneider Date: Mon, 28 Sep 2026 12:15:03 -0300 Subject: docs: data's truncation is pardes's own, a second write inserts, and a waiting pty/run is cancelled Review asked the docs to say what a script trips on: acme ignores OTRUNC on data (fsys.c:543), so truncating it is an extension; addr sits past each write, so a second echo x > data inserts after the first; and a pty/run line waiting for a fresh terminal's first prompt waits for ever if none is drawn, so the way out is to interrupt the read. The lock's retry advice was already there. Co-Authored-By: Claude Opus 5.5 --- src/fs-help.txt | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) (limited to 'src') diff --git a/src/fs-help.txt b/src/fs-help.txt index bbff6f13..689d8839 100644 --- a/src/fs-help.txt +++ b/src/fs-help.txt @@ -36,7 +36,7 @@ Below, $m is the mount (/mnt/9p/pardes/ via 9ns --mntgen; PARDES_MOUNT in a Pitfalls, one each: Each open of pane/new makes another pane (ls, stat, find never do); rmdir closes even a dirty one. addr takes #n,#m or sam-style /regexp/ (^ $ per line); a failed one makes data refuse until reset. - data: > replaces just the addr range and : > deletes it; body: > empties the whole buffer. + data: > replaces the addr range, : > deletes it, a 2nd > inserts (addr moved); body: > empties all. tag reads the path, then the tag's own text; writes append to that text; truncating clears it. A terminal's body is a history snapshot frozen per open; pty/data is the live stream. exec: a word no builtin knows is typed into a terminal in the pane's directory, and not an error. -- cgit v1.3