chime/tests/test-chime-intervals-for-marker.el, branch mainEmacs chimes, notifications, and modeline reminders so you don't miss events
https://git.cjennings.net/chime/atom?h=main2026-05-11T10:40:24+00:00feat: add per-event :CHIME_NOTIFY_BEFORE: interval override2026-05-11T10:40:24+00:00Craig Jenningsc@cjennings.net2026-05-11T10:40:24+00:00urn:sha1:ee90de269e4f65a9b57b4fc9e260d3aa6948b6ca
Chime's migration from org-wild-notifier dropped the per-event notify-before property, so a heading could no longer override the global chime-alert-intervals. I brought it back.
A heading's :CHIME_NOTIFY_BEFORE: N (a non-negative integer) means "notify once, N minutes before, severity medium" and replaces chime-alert-intervals for that event. The org-wild-notifier name :WILD_NOTIFIER_NOTIFY_BEFORE: still works, as a deprecated alias. When it supplies the value, chime emits one per-session warning pointing at the new name. :CHIME_NOTIFY_BEFORE: wins when both are set. A malformed value logs a message naming the heading and falls back to the global.
chime--gather-info reads the property in the async child. The deprecation flag rides on the event alist so the parent emits the warning without changing the async return contract.
I also touched two test files. test-chime-async-helpers.el's fixtures fed bare symbols where chime--handle-async-success now expects event alists, so they build real events via chime--make-event. And the new test file's message-capture macro had a lexical-scoping bug (the captured list was invisible after the macro returned), so the two affected tests inline the capture and the macro is gone.
test: add failing tests for per-event interval override2026-05-11T10:02:17+00:00Craig Jenningsc@cjennings.net2026-05-11T10:02:17+00:00urn:sha1:73faba8658ea783bca8392e4d4cc14cf7f94a48f
I added fifteen tests ahead of the implementation, covering the per-event :CHIME_NOTIFY_BEFORE: property and the deprecated :WILD_NOTIFIER_NOTIFY_BEFORE: alias: value-string parsing (chime--parse-notify-before-value), property lookup with global fallback (chime--intervals-for-marker), the gather path (chime--gather-info honoring the property and flagging the alias on the event), and the once-per-session deprecation warning (chime--maybe-warn-deprecated-properties).
They all fail with void-function for the not-yet-defined helpers, plus a length mismatch on the gather-info tests since chime--gather-info still uses the global chime-alert-intervals.