aboutsummaryrefslogtreecommitdiff
path: root/modules/prog-training.el
diff options
context:
space:
mode:
authorCraig Jennings <c@cjennings.net>2026-05-25 16:02:35 -0500
committerCraig Jennings <c@cjennings.net>2026-05-25 16:02:35 -0500
commit9aa180ea57f79f79c156a0956677e13c5263b478 (patch)
tree8096c4afd1e8f81f23de1e7ecab3829c1e50c2c1 /modules/prog-training.el
parent374ccaee657425e1dadc9aa40095abbd0a42f5a1 (diff)
downloaddotemacs-9aa180ea57f79f79c156a0956677e13c5263b478.tar.gz
dotemacs-9aa180ea57f79f79c156a0956677e13c5263b478.zip
feat(ui-theme): default the theme fallback to bundled dupre
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.
Diffstat (limited to 'modules/prog-training.el')
0 files changed, 0 insertions, 0 deletions