The tree's README and fs.md answer round 8's doc questions

The README's log line names newcol, delcol, ask, restored and restoredcol;
it says what $m is under 9ns --unix; and a build that embeds no sources no
longer lists src/ (derived from the build, and tested). fs.md says what the
rest of a typed line does after Kill for each shell (fish runs on, bash
abandons it), that Exec <text> in a .py pane runs a command and never the
REPL, and why appending to a tag wants printf and a leading blank.

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

1 files changed, 11 insertions, 5 deletions

diff --git a/docs/fs.md b/docs/fs.md
index 46fe9f86..742506f1 100644
--- a/docs/fs.md
+++ b/docs/fs.md
@@ -181,8 +181,10 @@ in a shell running without job control (`set +m`) the job shares the
 shell's group, so there is none to signal: Kill says `Kill: no job to
 signal`, and a write of it to `ctl` fails with that; with nothing running
 it says `Kill: nothing running`; and, of a typed line, only the
-foreground job, so of `sleep 30; echo done` typed at a prompt the `echo`
-still runs once the `sleep` is stopped --
+foreground job, after which what the rest of the line does is the shell's
+affair: of `sleep 30; echo done` typed at a prompt, fish goes on and runs
+the `echo`, and bash abandons the line, as each does when a job it waits
+on is killed --
 and reads every setting there is, one a line, in the words a write of it
 takes (`Verbose on`, `WindowOpacity 70`, `PanelSlide off`, `DumpDir
 <the directory in effect>`, `LocationsConfig ...`), so writing what it reads
@@ -344,7 +346,9 @@ terminal's while a program other than its shell holds the tty -- after
 Ctrl-D the shell would run the text, so nothing is sent and the pane says
 so. Still commands, whatever is bound: a word in a tag (so
 the tag is how to run `make` from that file), `Exec <text>` run by name
-(typed, a 2-1 chord onto `Exec`, a `ctl` line) and a command word @`cmd` in
+(typed, a 2-1 chord onto `Exec`, a `ctl` line) -- in a `.py` pane bound to
+a REPL, `Exec print(1)` runs `print(1)` as a command, never in the REPL --
+and a command word @`cmd` in
 the text, looked at or clicked (`# @`pytest -x`` in a script). A 9P `exec`
 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~`,
@@ -544,8 +548,10 @@ words (`Del`, `Put` and the rest) with it, since they are that text until
 you edit it, so `echo Make > tag` leaves only `Make` -- a truncating write
 drops the one newline that ends what it wrote, which would draw an empty
 row, and keeps any other; append with `>>` to
-keep them, with `printf ' Make' >> tag`: `echo` ends its word with a
-newline, which starts a new line of the tag. The clearing is an edit of the tag like a typed one and its undo
+keep them, with `printf ' Make' >> tag`. The leading blank is needed: the
+tag reads back with no blank after its last word, so `printf Make >> tag`
+glues `Make` onto it; and `echo ' Make' >> tag` ends with a newline, which
+starts a new line of the tag. The clearing is an edit of the tag like a typed one and its undo
 history is kept: `u` in the tag brings back the text it cleared, words
 included.