<feed xmlns='http://www.w3.org/2005/Atom'>
<title>dotemacs/tests/test-ui-theme-commands.el, branch main</title>
<subtitle>My Emacs configuration
</subtitle>
<id>https://git.cjennings.net/dotemacs/atom?h=main</id>
<link rel='self' href='https://git.cjennings.net/dotemacs/atom?h=main'/>
<link rel='alternate' type='text/html' href='https://git.cjennings.net/dotemacs/'/>
<updated>2026-05-25T21:02:35+00:00</updated>
<entry>
<title>feat(ui-theme): default the theme fallback to bundled dupre</title>
<updated>2026-05-25T21:02:35+00:00</updated>
<author>
<name>Craig Jennings</name>
<email>c@cjennings.net</email>
</author>
<published>2026-05-25T21:02:35+00:00</published>
<link rel='alternate' type='text/html' href='https://git.cjennings.net/dotemacs/commit/?id=9aa180ea57f79f79c156a0956677e13c5263b478'/>
<id>urn:sha1:9aa180ea57f79f79c156a0956677e13c5263b478</id>
<content type='text'>
The fallback kicks in when persist/emacs-theme is missing — a fresh machine, or one that's never saved a theme. It was modus-vivendi, which ships with Emacs but has none of the dimming colors this config chooses, so an unconfigured machine looked and dimmed differently from a configured one. I hit exactly that on a second box this week.

dupre is bundled in themes/ and carries those colors, and it loads wherever this config does, so it's the better default. I added a regression test asserting the default is dupre; its loadability is already covered by test-dupre-theme.el. The docstring no longer claims the fallback must be a built-in theme, since dupre isn't one.
</content>
</entry>
<entry>
<title>test(ui-theme): cover switch-themes, save-to-file, get-active-name</title>
<updated>2026-05-14T09:08:51+00:00</updated>
<author>
<name>Craig Jennings</name>
<email>c@cjennings.net</email>
</author>
<published>2026-05-14T09:08:51+00:00</published>
<link rel='alternate' type='text/html' href='https://git.cjennings.net/dotemacs/commit/?id=0aca95e94b7ebc1837f5b3fc6ed97937695b3558'/>
<id>urn:sha1:0aca95e94b7ebc1837f5b3fc6ed97937695b3558</id>
<content type='text'>
</content>
</entry>
</feed>
