diff options
| author | Gabriel Schneider <[email protected]> | 2026-09-29 02:33:04 -0300 |
|---|---|---|
| committer | Gabriel Schneider <[email protected]> | 2026-10-01 00:12:15 -0300 |
| commit | d0500fe7ecd6149ffafe6a04ff2b8206ff6c52df (patch) | |
| tree | f3499a63d18435fe8f546ef723491d4ea369a046 /docs/fs.md | |
| parent | 672b2643583d13feef5d47600e0f6c15f276fba2 (diff) | |
| download | pardes-d0500fe7ecd6149ffafe6a04ff2b8206ff6c52df.tar.gz pardes-d0500fe7ecd6149ffafe6a04ff2b8206ff6c52df.zip | |
The docs say sel is writable, Edit blocks may span writes, and sig INT stops a REPL
sel's write was documented in fs.md only; the skill says it now. With
command lines held per open, an Edit block may come in several writes (a
shell's line-at-a-time printf), so the heredoc advice goes. Kill never
stopped what a REPL runs, since pardes did not start it; the docs point at
pty/ctl sig INT.
Co-Authored-By: Claude Opus 5.5 <[email protected]>
Diffstat (limited to 'docs/fs.md')
| -rw-r--r-- | docs/fs.md | 8 |
1 files changed, 5 insertions, 3 deletions
@@ -368,7 +368,9 @@ and its last line is indented, a second `\r`: one Enter leaves such a block open; a middle click does all of this itself, holding the Enter until the REPL answers the paste), since line by line a blank line ends a Python block and Python 3.14's REPL auto-indents each line typed into it. The REPL gets the text -wherever it is -- at a `pdb` or `input()` prompt too. Bindings are not dumped, so a Restore leaves none. +wherever it is -- at a `pdb` or `input()` prompt too. `Kill` does not stop +what a REPL runs, since pardes did not start it; `sig INT` on the REPL +pane's `pty/ctl` interrupts it as Ctrl-C would. Bindings are not dumped, so a Restore leaves none. The root's pair clicks at the active pane and `/pane/<n>/look` and `/pane/<n>/exec` at that pane; `/tagexec` and `/col/<n>/exec` click in the @@ -487,8 +489,8 @@ nothing. A write is one message a line, except that an `Edit` line takes the lines after it while its `{` group is open or its `a`, `c` or `i` text block waits for its `.` line, on a pane's `ctl`, the root's (at the active pane) and `exec` alike; an unclosed group is refused (``unmatched `{'``). -bash's builtin `printf` writes a line at a time, so write a block with a -heredoc or `env printf`. +A block may come in several writes on one open (bash's builtin `printf` +writes a line at a time): the open holds it until it ends (below). A line number counts newlines as sam's lineaddr does (editors/sam/ address.c:180), so the empty line just past a text's last newline is an |