diff options
Diffstat (limited to 'docs/fs.md')
| -rw-r--r-- | docs/fs.md | 13 |
1 files changed, 9 insertions, 4 deletions
@@ -137,7 +137,8 @@ gives each column's serial and its index left to right, and the log says `newcol <serial>` and `delcol <serial>` as columns come and go, and after a Restore `restoredcol <old> <new>` for each column as `restored` does for panes. Joincol folds a column into the one on its right, which keeps its own -serial and tag; the joined one's serial is gone (`delcol`). The root ctl +serial and tag; the joined column's panes go below that column's own, in +their order, and its serial is gone (`delcol`). The root ctl takes no column word: its `Delcol` is refused, pointing at `col/<serial>/ctl`. @@ -357,8 +358,9 @@ is no gesture and is never sent: a script writes to the REPL pane's `pty/data`, multi-line code as a bracketed paste (`\e[200~<code>\e[201~`, then `\r` in a write of its own once the REPL has echoed the paste -- Python 3.13's REPL takes an Enter read with the paste as part of it, even a -one-line one -- and a second `\r` when its last line is indented: one Enter -leaves a block open, pasted or typed; a middle click does all of this +one-line one -- and, only when the pasted code does not end in a newline +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. @@ -627,7 +629,10 @@ tag gives offsets into the whole tag as `tag` reads it, the path first.) An open freezes the ring's text the way `/screen` freezes a frame: reads walk it and end. Writing `follow` to that same open makes reads past it wait for the next record, one per read; a follower the ring outran reads `lost N` first. -Closing the open is the only way back, as with rio's `consctl`. +Closing the open is the only way back, as with rio's `consctl`. A follower +misses nothing within a session only: a Restore hangs its connection up +(and a 9ns mount with it, which must be restarted), so it dials again and +reads the new log from its `restore <path>`. A read with nothing to give yet -- a following `log`, `event`, `pty/data`, a `pty/run` before its answer -- is held, the way factotum holds its log's reads |