aboutsummaryrefslogtreecommitdiffstats
path: root/AGENTS.md
diff options
context:
space:
mode:
Diffstat (limited to 'AGENTS.md')
-rw-r--r--AGENTS.md16
1 files changed, 11 insertions, 5 deletions
diff --git a/AGENTS.md b/AGENTS.md
index fd40b57..0665bb9 100644
--- a/AGENTS.md
+++ b/AGENTS.md
@@ -16,13 +16,19 @@ the record of what changed and where the backups are.
## One palette, many consumers
Colours are written down once. `palette/<scheme>.conf` holds them under the
-scheme's own names, `palette/roles-<scheme>.conf` says what each is for, and
-`palette/roles.conf` is a single `scheme = ` line selecting the pair.
-`bin/udt-palette` renders that into every consumer's own syntax; `install.sh`
-runs it first, before anything is linked.
+scheme's own names and `palette/roles-<scheme>.conf` says what each is for.
+`bin/udt-palette` renders that pair into every consumer's own syntax;
+`install.sh` runs it first, before anything is linked.
+
+**The scheme selection lives outside the repo**, in `~/.config/udt/roles.conf`,
+seeded from `palette/roles.conf.default` on a first install and never
+overwritten after. That is deliberate: which theme a machine runs is local
+state, so switching does not dirty the working tree and two machines sharing
+this repo can differ. It is the one exception to this repo holding the
+canonical copy of everything.
Four schemes ship: `macchiato`, `tokyo-night`, `nord`, `dracula`. Switching is
-one line plus `./install.sh`.
+one line in `~/.config/udt/roles.conf` plus `./install.sh`.
Generated files are gitignored, because tracking them would turn every scheme
switch into a diff. Editing one is pointless: the next install overwrites it.