diff options
| author | Gabriel Schneider <[email protected]> | 2026-09-28 23:38:31 -0300 |
|---|---|---|
| committer | Gabriel Schneider <[email protected]> | 2026-10-01 00:12:15 -0300 |
| commit | 8469def61324feb5e278f88bebad36af7a0d997e (patch) | |
| tree | 2deeb598b94a517bfc977226d28cb7d0ffc11e4c /.agents | |
| parent | aae6fc630d9d77de9ad975414d003a55d5b9d1e3 (diff) | |
| download | pardes-8469def61324feb5e278f88bebad36af7a0d997e.tar.gz pardes-8469def61324feb5e278f88bebad36af7a0d997e.zip | |
A send to Python's REPL runs once, the Enter after the paste, not in it
A one-line send (print(1)) to Python 3.14 stopped at ... and needed another
Enter: its REPL takes a bracketed paste, and an Enter read in the same read
as the paste is part of the paste, one line or not (checked in a real pty).
Into a REPL that asked for bracketed paste, the Enters (two for an open
block) now wait for its next output, its answer to the paste, or 250 ms
with nothing. fs-test runs python3 in a real pty and checks a one-line exec
prints at once; the docs' pty/data recipe says to send the Enter apart.
Co-Authored-By: Claude Opus 5.5 <[email protected]>
Diffstat (limited to '.agents')
| -rw-r--r-- | .agents/skills/pardes-9p/SKILL.md | 8 |
1 files changed, 5 insertions, 3 deletions
diff --git a/.agents/skills/pardes-9p/SKILL.md b/.agents/skills/pardes-9p/SKILL.md index 39a6b1ce..b328334c 100644 --- a/.agents/skills/pardes-9p/SKILL.md +++ b/.agents/skills/pardes-9p/SKILL.md @@ -149,9 +149,11 @@ 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 +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`, +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 3.14's REPL auto-indents each line it is typed. Every refused 9P write adds an `err <serial|-> <file>: <why>` record to `$m/log`; through a mount the write itself only says `Invalid argument`. |