v0.1.34
What's new
The file peek can now explain itself.
A blank peek — panel open, header filled in, no text — looks exactly the same
whether the file couldn't be read, the syntax highlighter returned nothing
usable, the colours came out invisible against your background, or the text
never got laid out. That made it effectively impossible to act on a report.
- Copy diagnostics — a new button in the peek's footer puts the recent
viewer log, plus your build and macOS version, on the clipboard. If a peek
ever comes up blank, paste that into an issue and it says which step emptied
it. - The same lines go to the macOS unified log, so they can also be collected
after the fact:
log show --last 15m --predicate 'subsystem == "co.webteractive.zetty"' --style compact - Opening a file that turns out to be missing or to be a directory is no longer
silent when it comes from ⌘-click or the file tree.
Nothing is sent anywhere, and the file's own contents are never recorded — only
counts (how many characters, how many of them are visible ink, which colours
were used).