aboutsummaryrefslogtreecommitdiffstats
path: root/palette
diff options
context:
space:
mode:
authorDanilo M. <danix@danix.xyz>2026-09-11 17:42:14 +0200
committerDanilo M. <danix@danix.xyz>2026-09-11 17:42:14 +0200
commit90d92490f83156a4a90c44b3837f1037cec80132 (patch)
treee3ab0a62466b72120a63793a886ff19d5e28b8a4 /palette
parent81f7686fe7d8edc5c020f33e8766d4de7c5beccd (diff)
downloadunified-desktop-theme-90d92490f83156a4a90c44b3837f1037cec80132.tar.gz
unified-desktop-theme-90d92490f83156a4a90c44b3837f1037cec80132.zip
feat(palette): move the scheme selection out of the repo
The selector was tracked at palette/roles.conf, which made switching scheme a committable change: the previous commit carried `scheme = tokyo-night` in its diff purely because that was the theme running at the time. Which theme a machine runs is local state, not a property of the project, so the live file is now ~/.config/udt/roles.conf. install.sh seeds it from palette/roles.conf.default on a first run and never overwrites it, so a switch leaves the working tree clean and two machines sharing this repo can run different schemes. udt-palette falls back to the seed when no live file exists, so a bare checkout still generates. This is the one exception to the repo holding the canonical copy of everything, and AGENTS.md says so. Verified: seeding on a missing file, the seed not overwriting an existing choice, generation from the seed alone, and both selftests. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_015gbjA2bmswN8jyPDKzrvqe
Diffstat (limited to 'palette')
-rw-r--r--palette/roles.conf14
-rw-r--r--palette/roles.conf.default21
2 files changed, 21 insertions, 14 deletions
diff --git a/palette/roles.conf b/palette/roles.conf
deleted file mode 100644
index a1ca448..0000000
--- a/palette/roles.conf
+++ /dev/null
@@ -1,14 +0,0 @@
-# Scheme selection.
-# Copyright (C) 2026 Danilo M. <danix@danix.xyz>
-# Licensed under the GNU General Public License v2 only.
-#
-# This is the one line to change to retheme the desktop. It picks a pair of
-# files: palette/<scheme>.conf, which holds the colours under the scheme's own
-# names, and palette/roles-<scheme>.conf, which says what each colour is for.
-#
-# Run ./install.sh afterwards. Every themed config is generated from that pair,
-# so nothing else needs editing.
-#
-# Available: macchiato, tokyo-night, nord, dracula
-
-scheme = tokyo-night
diff --git a/palette/roles.conf.default b/palette/roles.conf.default
new file mode 100644
index 0000000..556ef56
--- /dev/null
+++ b/palette/roles.conf.default
@@ -0,0 +1,21 @@
+# Scheme selection.
+# Copyright (C) 2026 Danilo M. <danix@danix.xyz>
+# Licensed under the GNU General Public License v2 only.
+#
+# This file is the SEED. install.sh copies it to ~/.config/udt/roles.conf on a
+# first run and never touches it again, so edit the copy, not this one.
+#
+# The live file picks a pair: palette/<scheme>.conf, which holds the colours
+# under the scheme's own names, and palette/roles-<scheme>.conf, which says
+# what each colour is for.
+#
+# $EDITOR ~/.config/udt/roles.conf # change the scheme line
+# ./install.sh # regenerate every config
+#
+# Keeping the selection outside the repo means switching scheme does not dirty
+# the working tree, and two machines sharing this repo can run different
+# schemes.
+#
+# Available: macchiato, tokyo-night, nord, dracula
+
+scheme = macchiato