A terminal is typed into only when idle at an empty prompt

A look at a directory, or an exec at a terminal, typed its line after
whatever sat unsent at the prompt and ran the two joined (`echo TYPEDls`).
A terminal with text at its prompt now takes no line; a look at its
directory opens a new terminal, an exec runs as a command pane.

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

1 files changed, 9 insertions, 5 deletions

diff --git a/docs/fs.md b/docs/fs.md
index cfc8e656..49685888 100644
--- a/docs/fs.md
+++ b/docs/fs.md
@@ -350,7 +350,8 @@ same tree without leaving the process.
 `/look` and `/exec` are the editor's two clicks, one per line of a write:
 
 - a line written to `look` is a right click on it: a path opens a file,
-  `file:12` jumps to a line, a directory opens a terminal there that runs
+  `file:12` jumps to a line, a directory types `ls` into a terminal idle
+  at an empty prompt there, else opens a terminal there that runs
   `ls` once (pardes has no directory listing pane of acme's kind; a shell
   in it is where one goes on from a directory), a URL opens in the
   browser, and a plain word, as acme's look3 does, selects its next
@@ -371,10 +372,13 @@ same tree without leaving the process.
   acme's makenewwindow puts a new window (util.c:456-467: the active column
   first, then the pane's own), under the text with room or halving the
   tallest, never shorter than its tag and 2 rows),
-  or anything else, a command line. Written at a terminal at its prompt it
-  is typed into that shell (and a terminal whose shell exits, `exit` typed
-  or run, closes its pane). From anywhere else -- a file, a scratch, a tag,
-  a terminal whose tty a program holds -- it runs as a command pane: a
+  or anything else, a command line. Written at a terminal idle at an EMPTY
+  prompt it is typed into that shell -- any line that is no builtin, so
+  `Delcol x` at a terminal goes to the shell -- (and a terminal whose shell
+  exits, `exit` typed or run, closes its pane). Nothing is ever typed over
+  text someone typed at a prompt and did not send. From anywhere else -- a
+  file, a scratch, a tag, a terminal with a line typed at its prompt or
+  whose tty a program holds -- it runs as a command pane: a
   terminal whose child is the root ctl's `Shell` ($SHELL, else /bin/sh, unless set) run
   with `-c` and the line, in the pane's directory, with job control on
   (bash, sh, dash, zsh, ksh `-m`; fish `status job-control full`),