l0ng-ai 005efee058 fix(ui): explain the io errors that build their own message ...

`explain_io` exists because "Permission denied (os error 13)" answers a
developer's question and not the reader's — its own doc says so. Every
failure routed through `HostOps::notify_err` gets it. Four that build
their notification string by hand did not, and printed the raw error.

The clearest symptom was inside one file: saving a file in the editor
went through `notify_err` and explained itself, while opening the same
file, denied for the same reason, said `os error 13`. Both file-link
openers are changed together — the file tree's opener deliberately shares
its wording with the terminal's (#542), so explaining one and not the
other would have split a pairing that was on purpose.

The `log::warn!` next to each call keeps the exact error. A developer
reading a log and a person who just lost a save want different things,
so both are written rather than one chosen — noted on `explain_io` along
with the rule, since it was the absence of a stated rule that let four
callers drift.

2026-08-16 00:52:02 +08:00

..

bin

feat(update): update an all-users Windows install through one UAC prompt (#562)

2026-08-13 18:13:20 +08:00

core

refactor: drop eight #[allow(dead_code)] that no longer allow anything

2026-08-15 20:06:13 +08:00

terminal

fix(ui): explain the io errors that build their own message

2026-08-16 00:52:02 +08:00

ui

fix(ui): explain the io errors that build their own message

2026-08-16 00:52:02 +08:00

daemon.rs

chore: strip every comment from the Rust sources (#268)

2026-07-30 21:36:15 +08:00

main.rs

Retire to the tray on window close; cold start no longer stalls on stale daemon files (#639)

2026-08-14 23:04:15 +08:00