Save makes the directories its file goes in, always: for the pane's own name and Save path alike

Whether a Save made missing directories depended on how the name had
come about. Config's pane did, a name written into a missing directory did
(since kkrqxtsp), and `Save path` and every other name did not, failing
ENOENT instead. There is now one rule: a Save makes the parent
directories of the file it writes, a pane's own or a terminal's
scrollback included, and the make_dirs flag is gone. A directory it
cannot make still fails the write with why, as fs.py's
/nonexistent-pardes-dir case shows. fs.py now also saves into missing
directories by Save path and by a written name.

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

1 files changed, 0 insertions, 4 deletions

diff --git a/src/File.zig b/src/File.zig
index 43b921e3..84cec879 100644
--- a/src/File.zig
+++ b/src/File.zig
@@ -61,10 +61,6 @@ pub const State = struct {
     /// edit to another length cannot be back to it, and is not hashed.
     saved_len: ?usize = null,
     watch_after_save: bool = false,
-    /// Save makes the file's directory, and any above it, first: `Config`'s
-    /// pane for an init file that is not there yet, whose directory may not
-    /// be either.
-    make_dirs: bool = false,
     /// The file changed on disk under unsaved edits, which were kept (see
     /// `changed`): its hash, so the same change is said once, until a Save
     /// or get settles it. A Save warns once before overwriting it, as acme's