Parker 0.4.4

When a note changes underneath you

Parker reloads an open note when the file changes on disk — a git pull, another machine, another editor. Until now it did that silently, and if you had unsaved edits it quietly kept yours and let autosave write over the other version.

Now the lines a reload rewrote are marked in amber — line, number and gutter — and they stay until you type in that note. Not a flash: a mark you can still read when you come back from lunch. A chip in the status bar counts the notes waiting to be read.

When the file changed while you were editing, a bar asks instead of deciding: Use disk version or Keep mine. Autosave holds off on that note until you answer.

The tab dot now says what state a note is in

One dot, one colour: dimmed green when saved, cyan for your unsaved typing, amber for text that arrived from outside, purple for a conflict, red when a read or write failed — a failure that used to reach only the console.

Selection

Line numbers brighten along with a multi-line selection, and the selection itself now hugs the text instead of filling the line.

Note on first launch

The app is ad-hoc signed, so macOS shows a Gatekeeper warning the first time you open it, and asks again for access to your Documents folder after each update.