aboutsummaryrefslogtreecommitdiff
path: root/githooks/pre-commit
diff options
context:
space:
mode:
authorCraig Jennings <c@cjennings.net>2026-05-25 11:54:39 -0500
committerCraig Jennings <c@cjennings.net>2026-05-25 11:54:39 -0500
commit54606fe673119434905af8dd8a2a6fca6635f112 (patch)
tree7560a54ecf9f22ab70c9bbbcac167e2f04ce0b4d /githooks/pre-commit
parent8c71e8c80f4e7d5d4be4c2ee555d20b00514852f (diff)
downloaddotemacs-54606fe673119434905af8dd8a2a6fca6635f112.tar.gz
dotemacs-54606fe673119434905af8dd8a2a6fca6635f112.zip
fix(theme): register dupre faces so org status colors are themed
The dupre theme defined its own faces (dupre-accent, the headings, and the org status faces) only through custom-theme-set-faces, never defface. That leaves them unregistered, so they render through :inherit but silently fail when applied directly as a text property. org-todo-keyword-faces and org-priority-faces apply faces that way, so the org keyword and priority colors never showed as dupre tones. I added a defface registration block to dupre-faces.el for all of dupre's own faces, so they're real faces. The theme still sets their colors. Then I pointed org-todo-keyword-faces and org-priority-faces (in org-config.el) at named dupre-org-* faces, each the closest palette color to its former hard-coded name, and gave each a dimmed variant that auto-dim-config.el swaps in for unfocused windows. A keyword in a dimmed window now shows a darker shade of its own color rather than flat gray or full brightness. A regression test asserts dupre's faces stay registered, since that was the latent bug behind all of this.
Diffstat (limited to 'githooks/pre-commit')
0 files changed, 0 insertions, 0 deletions