A command line runs as its own command pane unless it is clicked at a shell's prompt

A middle click, an exec write or a tag word that no builtin knows was typed
into some terminal for the pane's directory, sharing whatever state that
shell was in and answering nothing, so a misspelling vanished into a shell.
Now only a line clicked at an interactive terminal's prompt is typed there.
From anywhere else it runs as a command pane: a terminal whose child is
$SHELL -c the line in the pane's directory, full emulation, which shows its
output and then exit N from the host's reaping of the child, and stays. A
finished command pane is the next command's for its directory, which runs
below what it showed after a '% line' line (acme appends to +Errors and never
clears it, util.c:213); a running one gets a second pane. Kill ends a command
pane's whole process group, the log records run and exit, exec reads back the
command pane's serial, and a line is at most 1 KB, read off the pane as the
host forks rather than carried in every spawn effect. ttyForDir's search for
a free shell is gone. The goldens of chordcut, cmdword and layout-open change
where a file's exec now opens a command pane, and ttytaken is rewritten to
exec from the terminal itself; docs/open-questions.md records the decision.

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

1 files changed, 8 insertions, 4 deletions

diff --git a/.agents/skills/pardes-9p/SKILL.md b/.agents/skills/pardes-9p/SKILL.md
index 63dec104..df53c90f 100644
--- a/.agents/skills/pardes-9p/SKILL.md
+++ b/.agents/skills/pardes-9p/SKILL.md
@@ -60,7 +60,7 @@ $m/focus      the serial of the pane with the keyboard (empty while a column/wor
               echo a serial into it to move the keyboard (a folded pane stays folded)
 $m/ctl        the settings, one a line as a write takes them; write a setting or a session builtin
               (Newcol, Dump, Theme x; Exit QUITS the editor, Kill [word...] stops the
-              commands pardes typed into terminals; Exit and Restore refuse once per
+              commands pardes started (command panes, lines it typed into shells); Exit and Restore refuse once per
               unsaved pane, `<name>: Modified (Exit again to discard)`, and the same
               word again DISCARDS that text -- not a retry, unlike lock's `file in use`;
               Kill signals only the foreground job, so of `sleep 30; echo done` the
@@ -117,9 +117,13 @@ active pane from the root and at that pane from `$m/pane/<n>/look` and
 made, or the pane it focused or acted on. A command that fails is reported in
 the editor, not as a write error, so inspect the resulting pane, index, message
 or screen; only a malformed line fails the write itself. A word no builtin
-knows (a typo included) is typed into a terminal -- the pane itself if it is a
-terminal at its prompt, else one in the pane's directory, made if need be --
-and is not reported as an error. Every refused 9P write adds an `err <serial|->
+knows (a typo included) is a command line: written at a terminal at its
+prompt it is typed into that shell; from anywhere else it runs as a command
+pane, a terminal whose child is `$SHELL -c` the line in the pane's
+directory, which ends showing `exit N` (a typo: `exit 127`) and logs `run
+<serial> <word>` and `exit <serial> <N|?>` -- `exec` reads back its serial,
+so follow `log` for the exit. The directory's next command reuses a finished
+command pane, below what it showed. Every refused 9P write adds an `err <serial|->
 <file>: <why>` record to `$m/log`; through a mount the write itself only says
 `Invalid argument`.