From ae71c2e2845be4a5595e7fae117c0ef22c16c0c0 Mon Sep 17 00:00:00 2001 From: Gabriel Schneider Date: Tue, 29 Sep 2026 09:59:58 -0300 Subject: The docs: --detach runs the editor as $!, a line with no newline fails only in the log, data reads to the end The skill said --detach forks and $! was not the editor's pid; it is, and /status agrees. A line written with no newline runs at the close, after the write is answered, so its failure is in the log alone: end lines with their newline. And `cat data` reads from the address to the end of the text, as acme's does; xdata is the range. Co-Authored-By: Claude Opus 5.5 --- .agents/skills/pardes-9p/SKILL.md | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) (limited to '.agents') diff --git a/.agents/skills/pardes-9p/SKILL.md b/.agents/skills/pardes-9p/SKILL.md index 5ac1ba46..0575fab7 100644 --- a/.agents/skills/pardes-9p/SKILL.md +++ b/.agents/skills/pardes-9p/SKILL.md @@ -17,9 +17,9 @@ Check `$NINE_MOUNT` first. `9ns --mntgen` sets it for every process it starts (an interactive shell on this machine runs inside one), so a set `$NINE_MOUNT` means the posted-9P registry is mounted there, usually `/mnt/9p`, and each running editor is a directory `$NINE_MOUNT/pardes//` (a `--detach=NAME` -session's is `pardes/NAME/`; `pardes --detach=NAME` forks, its parent -returning at once, so the running editor's pid is not `$!`: read it from -`$m/status`, whose first line is `pid `). Inside a pane, `$PARDES_9P` is that session's +session's is `pardes/NAME/`; `pardes --detach=NAME &` runs the editor as +that process, so `$!` is its pid, and `$m/status`'s first line, `pid `, +says the same). Inside a pane, `$PARDES_9P` is that session's socket (`/run/user/1000/pardes-9p-.sock`), which names the directory either way, and `$PARDES_PANE` is the calling pane's serial: -- cgit v1.3