From 58aae9a1f7aca8e64814c8775b0c17bf93f4da0f Mon Sep 17 00:00:00 2001 From: Gabriel Schneider Date: Tue, 18 Aug 2026 15:13:50 -0300 Subject: nested + pardes: snapshot updates and small behavior fixes across panes --- docs/design.typ | 3 ++- docs/macos.md | 16 +++++++++------- 2 files changed, 11 insertions(+), 8 deletions(-) (limited to 'docs') diff --git a/docs/design.typ b/docs/design.typ index d49be3e6..0c91d15d 100644 --- a/docs/design.typ +++ b/docs/design.typ @@ -428,7 +428,8 @@ cannot clobber what the desktop was holding. A paste from an outer terminal arrives bracketed, as one `paste` event. *Tag.* Live prefix (mode indicator, cwd or path) + editable tail with the -full modal editor; defaults `New Del` / `Save New Del`; an image tag reports +full modal editor; defaults `New Del` / `Save New Del`, with `*` after an +unsaved file's name; an image tag reports `img petscii: palette: ascii: ` before the ordinary tail (its renderer toggles are builtins under `SPC t p/l/a`). Topbar: diff --git a/docs/macos.md b/docs/macos.md index 5e5f13e3..be110532 100644 --- a/docs/macos.md +++ b/docs/macos.md @@ -323,13 +323,15 @@ document, so focus landing on one clears the icon and puts the title back to icon: they are real paths, and a proxy icon is about the file, not about who may edit it. -The dirty half needed the one core change in all of this. `File` counted -`revision` but never recorded which edit was last *written*, so no shell could -derive "unsaved" — `File.saved_revision` is that watermark, set by `Save` at -the moment the write is asked for. Nothing in the core renders it and no other -shell reads it; it exists because a windowed host has somewhere to put the -answer. It is marked at ask-time rather than on completion because `save_file` -carries none back, which makes it exactly as honest as the tagline already was. +The dirty half needed one core watermark. `File` counted `revision` but never +recorded which edit was last *written*, so no shell could derive "unsaved" — +`File.saved_revision` is that watermark, advanced by `Save` at the moment the +write is asked for and by a successful external-file reload whose bytes +already came from disk. The core renders the same answer as ` *` after the +path in every tagline, while this host also puts it in the native close button. +Save is marked at ask-time rather than on completion because `save_file` +carries none back, which makes both indicators exactly as honest as the Save +request. ## The menu bar, and the chords the core never sees -- cgit v1.3