summaryrefslogtreecommitdiff
path: root/.agents
diff options
context:
space:
mode:
authorGabriel Schneider <[email protected]>2026-09-29 08:25:27 -0300
committerGabriel Schneider <[email protected]>2026-10-01 00:12:16 -0300
commitf41599385cc0ee990954b32eca79984d54d0c5e3 (patch)
tree4e429dda6eb88119a91f08a798d4ad53cabdf88d /.agents
parent0bb3f6d4f71a3a10eba846ae3ab5064630b12201 (diff)
downloadpardes-f41599385cc0ee990954b32eca79984d54d0c5e3.tar.gz
pardes-f41599385cc0ee990954b32eca79984d54d0c5e3.zip
The docs: data writes replace their range, restored command panes show their exit, the tag's default words, empty matches at #0, errors' fallback, tagexec and event readers, Find finds names
Dogfood round 18 found these false: `>>` on data replaces the addressed range (acme's data write deletes then inserts); a restored command pane shows the `exit N` it ended with; the default tag words are `Save Tty Collapse Del`; `file:0/^/` passes over the empty match at #0; `errors` with no room logs msg records; a pane's tagexec never goes to an event reader; a scratch is named with `(pane N)` in a refusal; and /commands said Find searched the pane, where it finds file names. Co-Authored-By: Claude Opus 5.5 <[email protected]>
Diffstat (limited to '.agents')
-rw-r--r--.agents/skills/pardes-9p/SKILL.md3
1 files changed, 2 insertions, 1 deletions
diff --git a/.agents/skills/pardes-9p/SKILL.md b/.agents/skills/pardes-9p/SKILL.md
index 7f33937f..afdf3a4b 100644
--- a/.agents/skills/pardes-9p/SKILL.md
+++ b/.agents/skills/pardes-9p/SKILL.md
@@ -191,7 +191,8 @@ is followed by two, its argument and where it came from; write all three back
as read (one write or three) and it runs once with its argument. `Tty`'s argument is a shell
(`Tty fish`), and `Tty` on a pane's ctl opens a new terminal pane. After a
Restore, panes have new serials (`restored <old> <new>` in the log), a
-command pane shows `exit ?` and does not run again, and REPLs are unbound. Multi-line code
+command pane shows how it ended, `exit N` (`exit ?` if it was still running when
+dumped), and does not run again, and REPLs are unbound. Multi-line code
written to `pty/data` should be a bracketed paste, `\e[200~<code>\e[201~`,
then, in a separate write once the REPL has echoed the paste (Python 3.13+
takes a `\r` read with the paste as part of it, even for one line), `\r`.