The docs say which shell a command runs in, what Kill's word matches, where dumps go and in what time, and how to send code to a REPL

Dogfood found the docs saying $SHELL -c where commands run the root ctl's Shell, the README's log line missing run, exit, send, dump and restore, Kill's argument unexplained, and nothing on Repl - and bare Repl, on bracketed paste for multi-line code over pty/data, or on the UTC dump time. The Restore write's ECONNRESET through a mount is documented rather than fixed: pardes sends the answer before the hang-up, and 9ns drops it when its next send fails first. The REPL decision is recorded with the others, and the fs guide says a builtin's word still runs first.

Co-Authored-By: Claude Opus 5.5 <[email protected]>

1 files changed, 4 insertions, 4 deletions

diff --git a/src/fs-help.txt b/src/fs-help.txt
index 8948ac78..57ef7b62 100644
--- a/src/fs-help.txt
+++ b/src/fs-help.txt
@@ -5,11 +5,11 @@ index       one line per pane: serial, kind (text|term|pdf|image), dirty flag, n
 status      pid, version and pane count
 look        write a line: a right click on it at the active pane; read: the serials it touched
 exec        write a line: a middle click, an editor command word or a shell line; read the same
-log         events: new/del/rename/save <serial> <name>, msg <serial|-> <text>, err <serial|-> <why>
+log         events: new/del/rename/save <serial> <name>, run/exit/send <serial> ..., dump/restore <path>, msg, err
 screen      rendered screen as JSON, frozen from open to close
 listeners   the session's dial addresses
 focus       the serial of the pane with the keyboard; write a serial to give it the keyboard
-ctl         settings, one a line; or Newcol, Dump, Exit (quits; asks once), Kill (stops the fg job)
+ctl         settings, one a line; or Newcol, Dump, Exit (quits; asks once), Kill [word] (stops what pardes ran, or what starts with word)
 commands    every builtin: its word, arg if it takes one, and root or pane: which ctl takes it
 pane/new    open it to make a pane (named +New); the read answers that pane's serial
 pane/<n>/   name body tag ctl addr dot limit data xdata sel dirty mark scroll errors (write-only:
@@ -39,7 +39,7 @@ Pitfalls, one each:
   data: > replaces the addr range, : > deletes it, a 2nd > inserts (addr moved); body: > empties all.
   tag reads the path, then its own text; writes append; truncating clears it, default words too.
   A terminal's body is a history snapshot frozen per open; pty/data is the live stream.
-  exec: a non-builtin line runs as a command pane ($SHELL -c; exit N shown, logged), a shell's typed in.
+  exec: a non-builtin line runs as a command pane (ctl's Shell -c; exit N shown, logged), a shell's typed in.
   Through a mount a malformed write is EINVAL, a well-formed one that fails EIO: log's err says why.
   lock/unlock need a held ctl fd (exec 3>ctl), a held lock fails: retry. A column's last pane -> +New.
-  Repl python on a terminal's ctl: a .py body's clicks go to it; tag words, Exec x, @`x` stay commands.
+  Repl python on a terminal's ctl: a .py body's clicks go to it (Repl - unbinds, Repl says it); tags stay commands.