aboutsummaryrefslogtreecommitdiff
path: root/docs/CONFIGURATION.org
diff options
context:
space:
mode:
authorCraig Jennings <c@cjennings.net>2026-06-11 14:54:16 -0500
committerCraig Jennings <c@cjennings.net>2026-06-11 14:54:16 -0500
commite923bd652879bf361fb278349826ca99d09459f8 (patch)
tree04ad3928c577c5df3123c1037580dda6179dfdb3 /docs/CONFIGURATION.org
parentceb176e763962ce3d3bfa4275f36eef582f1c4d1 (diff)
downloadchime-e923bd652879bf361fb278349826ca99d09459f8.tar.gz
chime-e923bd652879bf361fb278349826ca99d09459f8.zip
docs: document chime-async-timeout and the frozen-modeline symptom
Diffstat (limited to 'docs/CONFIGURATION.org')
-rw-r--r--docs/CONFIGURATION.org19
1 files changed, 19 insertions, 0 deletions
diff --git a/docs/CONFIGURATION.org b/docs/CONFIGURATION.org
index 87ff0cf..a6dc979 100644
--- a/docs/CONFIGURATION.org
+++ b/docs/CONFIGURATION.org
@@ -383,6 +383,25 @@ Today's events always show if you launch Emacs after the alert time. This settin
(setq chime-max-consecutive-failures 0)
#+END_SRC
+** Async Fetch Timeout
+
+Event fetching runs in a background Emacs process. If that process never
+returns — for example, it hits an interactive prompt that batch mode can't
+answer — chime interrupts it after =chime-async-timeout= seconds, records
+the failure, and starts a fresh fetch on the next check. Without this
+watchdog, a hung fetch would silently block every subsequent check.
+
+#+BEGIN_SRC elisp
+;; Interrupt a fetch that runs longer than 2 minutes (default)
+(setq chime-async-timeout 120)
+
+;; Allow slower agenda scans more time
+(setq chime-async-timeout 300)
+
+;; Disable the watchdog entirely
+(setq chime-async-timeout nil)
+#+END_SRC
+
** Extra Alert Arguments
#+BEGIN_SRC elisp