refactor(themes): retire dupre, fall back to modus-vivendi

WIP, the theme-studio export, is the active theme. dupre was only the fallback and a structural reference. Move the fallback to the built-in modus-vivendi, guaranteed present everywhere this config loads. Delete the three dupre files plus its test and palette assets, and fix the stale comments that pointed at dupre-faces.el for the auto-dim and org-keyword faces (those moved to org-faces-config.el). Repoint the dupre-clear-theme spec's palette reference to git history.

1 files changed, 4 insertions, 5 deletions

diff --git a/modules/ui-theme.el b/modules/ui-theme.el
index a7873b9a5..8be3b4fdf 100644
--- a/modules/ui-theme.el
+++ b/modules/ui-theme.el
@@ -64,14 +64,13 @@ directory that is sync'd across machines with this configuration."
   :type 'file
   :group 'cj/ui-theme)
 
-(defcustom fallback-theme-name "dupre"
+(defcustom fallback-theme-name "modus-vivendi"
   "The name of the theme to fallback on.
 This is used when there's no file, or the theme name doesn't match
 any of the installed themes. It must be available wherever this config is
-loaded, since the fallback has no further fallback. dupre is bundled in
-themes/ and carries the dimming colors chosen for this config, so it is the
-default; a built-in theme like modus-vivendi works too but has no chosen
-dimming colors. If theme name is `nil', there will be no theme."
+loaded, since the fallback has no further fallback. modus-vivendi ships with
+Emacs, so it is present on every machine that loads this config, which makes
+it the right default. If theme name is `nil', there will be no theme."
   :type 'string
   :group 'cj/ui-theme)