A pane from pane/new is the session's directory's scratch, not the last active pane's

No pane asked for it, so borrowing the directory of whichever pane last
had the keyboard named it after an accident; acme's new window has acme's
directory.

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

1 files changed, 3 insertions, 1 deletions

diff --git a/docs/fs.md b/docs/fs.md
index 9ba9c0e4..0da2ccd0 100644
--- a/docs/fs.md
+++ b/docs/fs.md
@@ -71,7 +71,9 @@ for any process, and `$NINE_MOUNT/pardes/NAME/` a `--detach=NAME` session's.
 9ns exports `$NINE_MOUNT` to everything it starts, so a script checks that
 variable to know the mount is there, and takes the name from `$PARDES_9P`
 (`pardes-9p-<pid or NAME>.sock`). A new pane made through `pane/new` is a scratch named
-`<dir>/+New` until it is given a name. A column may hold no pane, as in acme:
+`<dir>/+New` until it is given a name, where `<dir>` is the session's
+directory (the one pardes started in), whichever pane last had the keyboard:
+no pane asked for it, as acme's new window has acme's directory. A column may hold no pane, as in acme:
 `Newcol` makes one empty, and closing a column's last pane leaves it empty
 with its tag holding the keyboard (`focus` reads empty) and logs only the
 `del`. `pane/new` places its pane as acme's makenewwindow(nil) does: in the