From 276a060dee5c753b513a75cca0b2c942dfe540fd Mon Sep 17 00:00:00 2001 From: Gabriel Schneider Date: Tue, 29 Sep 2026 12:24:12 -0300 Subject: A name cut across writes on one open is one name, applied once Each write to name was taken as a whole name, so a name a client wrote in two pieces renamed the pane twice, the first time to half a name. name's writes are now held per open, as exec's and ctl's lines are, until the newline or the close. Co-Authored-By: Claude Opus 5.5 --- docs/fs.md | 5 +++-- 1 file changed, 3 insertions(+), 2 deletions(-) (limited to 'docs/fs.md') diff --git a/docs/fs.md b/docs/fs.md index 3acee020..dc15ab91 100644 --- a/docs/fs.md +++ b/docs/fs.md @@ -554,8 +554,9 @@ writing it renames the buffer; a relative name resolves against the pane's directory. A name alone is no edit: the pane's `dirty` stays what its text made it (a renamed clean file is still 0, and nothing asks about it at Exit, Restore or Del, which ask only about text edited), and `Save` writes it -under the new name all the same. A write is one name: one trailing newline -is its end and nothing else is trimmed. A blank inside a name is taken +under the new name all the same. An open's writes are one name: held +until its newline, or its close when it has none, then applied once, however +the writes cut it; nothing else is trimmed. A blank inside a name is taken (`two words.zig`); refused, EINVAL, in acme's words (xfid.c:650) and why, are a blank at either end (not quietly cut off), `bad character in file name: a blank at its end`, a second line, `...: a newline (a name is one -- cgit v1.3