| Age | Commit message (Collapse) | Author | Files | Lines |
|
The lastmod range is inclusive at both ends and the stored revision
was reused as the next start, so the batch just notified matched
again. Start one revision later.
A subject can contain a newline, which broke the bullet rows and the
+N more count; flatten CR/LF to a space before escaping.
Also reconciles the state-write comment and spec with the actual
skip-and-advance failure behavior, and corrects two doc wordings.
|
|
A live test showed the old title ("<label> · N new") read poorly
and the body packed the rows into one block. Title is now
"New Mail - <label> (N)" with the mail-unread icon, and each
message is a bullet on its own line with a blank line between.
+N more counts rows, not physical lines, so the blank lines do
not skew it.
|
|
|
|
Stores the database UUID beside the revision, because notmuch
revisions only compare within one database and a rebuild restarts
the counter. Missing, corrupt or mismatched state reports nothing,
which the caller treats as seed-silently: with no floor, lastmod:0..
matches every unread message and startup becomes a wall of popups.
|
|
Three rows of author and subject, then +N more, which bounds the
height so a mailing list burst is not a wall. Markup characters are
escaped because dunst renders body markup and a subject is untrusted
text off the internet.
|
|
Same source the drawer parses, so adding an account in qtmaildir
notifies with no edit here. Keys run to the closing bracket because
real ones contain dots, and parsing walks lines because a folder
named [Gmail]/Bozze ends a section body early.
|
|
A library guard so the test can source the script for its pure
functions without starting a watch loop, and the check itself,
which is one bash script rather than a framework.
|