summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorGabriel Schneider <[email protected]>2026-09-28 10:13:45 -0300
committerGabriel Schneider <[email protected]>2026-10-01 00:12:14 -0300
commitae7aba431c1a152dc999e485e8285ebd285811f8 (patch)
treeaab8dd2504e0836da7c746d5a344843968d172e0
parent6dfe81c92ee532eb9e804dfda2fa05cc36515aa1 (diff)
downloadpardes-ae7aba431c1a152dc999e485e8285ebd285811f8.tar.gz
pardes-ae7aba431c1a152dc999e485e8285ebd285811f8.zip
docs: record dogfood evidence on unknown exec words in the open questions
Co-Authored-By: Claude Opus 5.5 <[email protected]>
-rw-r--r--docs/open-questions.md5
1 files changed, 5 insertions, 0 deletions
diff --git a/docs/open-questions.md b/docs/open-questions.md
index 9f4f44f5..db491213 100644
--- a/docs/open-questions.md
+++ b/docs/open-questions.md
@@ -32,6 +32,11 @@ and `%` set for it (`editors/acme/exec.c`, `run()` and its callers around
programs need a terminal of their own, and output goes to a `+Errors`-style
buffer rather than a live terminal.
+**Evidence from use (2026-09-28).** A fresh agent driving pardes through
+9P wrote a misspelled word to `exec`; it was typed into a terminal's fish
+shell ("Unknown command"), nothing reached `log`, and the write succeeded.
+Its report ranked this among the confusing behaviours.
+
**Related.** `pty/run` (see `docs/fs.md`) already gives an agent the second
behaviour inside a chosen terminal: a line in, `exit N` and its output out.
The planned root `ctl` (session builtins) and pane `ctl` (pane builtins)