aboutsummaryrefslogtreecommitdiff
path: root/docs
diff options
context:
space:
mode:
authorCraig Jennings <c@cjennings.net>2026-05-11 05:40:24 -0500
committerCraig Jennings <c@cjennings.net>2026-05-11 05:40:24 -0500
commitee90de269e4f65a9b57b4fc9e260d3aa6948b6ca (patch)
tree6f16459e8bf47a6925131ccc743b59e33cd9b9ae /docs
parent73faba8658ea783bca8392e4d4cc14cf7f94a48f (diff)
downloadchime-ee90de269e4f65a9b57b4fc9e260d3aa6948b6ca.tar.gz
chime-ee90de269e4f65a9b57b4fc9e260d3aa6948b6ca.zip
feat: add per-event :CHIME_NOTIFY_BEFORE: interval override
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.
Diffstat (limited to 'docs')
0 files changed, 0 insertions, 0 deletions