summaryrefslogtreecommitdiff
path: root/.agents
diff options
context:
space:
mode:
authorGabriel Schneider <[email protected]>2026-09-28 22:17:49 -0300
committerGabriel Schneider <[email protected]>2026-10-01 00:12:15 -0300
commit4793520998969439bb569c968c3143ae46aefc66 (patch)
tree2777799bd5f2cad34c3305b5ff50e2710040836c /.agents
parent754ffc99799c3a251634c1eff9a16eabbd73b31c (diff)
downloadpardes-4793520998969439bb569c968c3143ae46aefc66.tar.gz
pardes-4793520998969439bb569c968c3143ae46aefc66.zip
A pane's question is logged as ask, and answer on its ctl answers it
A script could not answer the several-REPLs question, which only a key could. Every question a pane asks on its notice band (which REPL takes an exec, Del's side from the keyboard) is now logged as `ask <serial> <what> <choices>`, and `answer <choice>` on the pane's ctl answers it as that key would, `answer -` taking it back as Esc does. One function answers for a key and for the ctl. Co-Authored-By: Claude Opus 5.5 <[email protected]>
Diffstat (limited to '.agents')
-rw-r--r--.agents/skills/pardes-9p/SKILL.md5
1 files changed, 4 insertions, 1 deletions
diff --git a/.agents/skills/pardes-9p/SKILL.md b/.agents/skills/pardes-9p/SKILL.md
index 845326d2..0b1ef70e 100644
--- a/.agents/skills/pardes-9p/SKILL.md
+++ b/.agents/skills/pardes-9p/SKILL.md
@@ -142,7 +142,10 @@ but never a 9P write: a script sends code by writing the REPL pane's
`pty/data`, and runs a command from such a file with `Exec <text>` or the
tag. A bound terminal's `ctl` line ends with its id (`python-a`); an event
record written back from such a file's body goes to its REPL, as the click
-would. `Repl -` unbinds; a bare `Repl` says the binding. Multi-line code
+would. `Repl -` unbinds; a bare `Repl` says the binding. With several
+REPLs bound for a language an exec asks which, logged `ask <serial> repl a b`
+(Del's side from the keyboard is `ask <serial> del k j`): answer with
+`echo 'answer a' > $m/pane/<serial>/ctl`, or `answer -` to send nothing. Multi-line code
written to `pty/data` should be a bracketed paste, `\e[200~<code>\e[201~`
then `\r`, and a second `\r` when the code's last line is indented (a `def`
or `for` body): one Enter leaves such a block open. Sent line by line, a blank line ends a Python block, and Python