<feed xmlns='http://www.w3.org/2005/Atom'>
<title>chime/docs, branch main</title>
<subtitle>Emacs chimes, notifications, and modeline reminders so you don't miss events
</subtitle>
<id>https://git.cjennings.net/chime/atom?h=main</id>
<link rel='self' href='https://git.cjennings.net/chime/atom?h=main'/>
<link rel='alternate' type='text/html' href='https://git.cjennings.net/chime/'/>
<updated>2026-07-09T23:06:06+00:00</updated>
<entry>
<title>docs: note that a running Emacs won't see a new ALSA config</title>
<updated>2026-07-09T23:06:06+00:00</updated>
<author>
<name>Craig Jennings</name>
<email>c@cjennings.net</email>
</author>
<published>2026-07-09T23:06:06+00:00</published>
<link rel='alternate' type='text/html' href='https://git.cjennings.net/chime/commit/?id=372b61dcce34778d8a8b59bc6f02a942455dc825'/>
<id>urn:sha1:372b61dcce34778d8a8b59bc6f02a942455dc825</id>
<content type='text'>
alsa-lib parses its configuration once per process, so an emacs --daemon started before the config landed keeps the old view. play-sound-file keeps failing there while it succeeds in a fresh emacs -Q, which reads as the system fix not having worked.

Hit this on my own daemon after adding the pipewire default symlink: nine hours' uptime, still no usable default PCM.
</content>
</entry>
<entry>
<title>docs: document sound-player selection and the ALSA device failure</title>
<updated>2026-07-09T18:48:06+00:00</updated>
<author>
<name>Craig Jennings</name>
<email>c@cjennings.net</email>
</author>
<published>2026-07-09T18:48:06+00:00</published>
<link rel='alternate' type='text/html' href='https://git.cjennings.net/chime/commit/?id=b24f7aee3116f0daa106e76c7ebb42716347136b'/>
<id>urn:sha1:b24f7aee3116f0daa106e76c7ebb42716347136b</id>
<content type='text'>
CONFIGURATION.org covers how the player is chosen and when chime-sound-device applies.

TROUBLESHOOTING.org names the "No usable sound device driver found" error, how to confirm it outside Emacs with aplay, and the two ways out: name a device that resolves, or repair the system so default routes to PipeWire.
</content>
</entry>
<entry>
<title>feat: add themeable faces to the modeline event display</title>
<updated>2026-06-24T02:56:05+00:00</updated>
<author>
<name>Craig Jennings</name>
<email>c@cjennings.net</email>
</author>
<published>2026-06-24T02:56:05+00:00</published>
<link rel='alternate' type='text/html' href='https://git.cjennings.net/chime/commit/?id=081d76e4b9935217d650ae142bce6e8200e97b48'/>
<id>urn:sha1:081d76e4b9935217d650ae142bce6e8200e97b48</id>
<content type='text'>
The modeline event text inherited the mode-line face with no way to style it. I added four faces (chime-modeline-face, chime-modeline-soon-face, chime-modeline-urgent-face, chime-modeline-no-events-face) that color the display by how soon the next event is.

Two thresholds, chime-modeline-soon-threshold-minutes (30) and chime-modeline-urgent-threshold-minutes (5), drive the urgency mapping. The default and idle faces inherit mode-line, so the modeline looks unchanged until you theme it. Soon inherits warning and urgent inherits error, so imminent events stand out across themes without configuration.
</content>
</entry>
<entry>
<title>docs: document chime-async-timeout and the frozen-modeline symptom</title>
<updated>2026-06-11T19:54:16+00:00</updated>
<author>
<name>Craig Jennings</name>
<email>c@cjennings.net</email>
</author>
<published>2026-06-11T19:54:16+00:00</published>
<link rel='alternate' type='text/html' href='https://git.cjennings.net/chime/commit/?id=e923bd652879bf361fb278349826ca99d09459f8'/>
<id>urn:sha1:e923bd652879bf361fb278349826ca99d09459f8</id>
<content type='text'>
</content>
</entry>
<entry>
<title>docs: document the per-event :CHIME_NOTIFY_BEFORE: property</title>
<updated>2026-05-11T10:51:29+00:00</updated>
<author>
<name>Craig Jennings</name>
<email>c@cjennings.net</email>
</author>
<published>2026-05-11T10:51:29+00:00</published>
<link rel='alternate' type='text/html' href='https://git.cjennings.net/chime/commit/?id=783c2abe7ca6e88e372dfbf86aae2cbaa321fed8'/>
<id>urn:sha1:783c2abe7ca6e88e372dfbf86aae2cbaa321fed8</id>
<content type='text'>
The README's migration note said the per-event reminder property had been removed. That's stale now that the property is back. I rewrote the line to point at :CHIME_NOTIFY_BEFORE: and the deprecated :WILD_NOTIFIER_NOTIFY_BEFORE: alias. I also added a "Per-Event Override" section to docs/CONFIGURATION.org covering the syntax, the no-inheritance behavior, malformed-value handling, and the alias's deprecation path.
</content>
</entry>
<entry>
<title>docs: split detailed user docs out of readme</title>
<updated>2026-05-10T21:36:31+00:00</updated>
<author>
<name>Craig Jennings</name>
<email>c@cjennings.net</email>
</author>
<published>2026-05-10T21:36:31+00:00</published>
<link rel='alternate' type='text/html' href='https://git.cjennings.net/chime/commit/?id=0772736d2bca36472f623d5258784f41db9b4f9a'/>
<id>urn:sha1:0772736d2bca36472f623d5258784f41db9b4f9a</id>
<content type='text'>
</content>
</entry>
</feed>
