From 90d92490f83156a4a90c44b3837f1037cec80132 Mon Sep 17 00:00:00 2001 From: "Danilo M." Date: Fri, 11 Sep 2026 17:42:14 +0200 Subject: 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 Claude-Session: https://claude.ai/code/session_015gbjA2bmswN8jyPDKzrvqe --- palette/roles.conf | 14 -------------- 1 file changed, 14 deletions(-) delete mode 100644 palette/roles.conf (limited to 'palette/roles.conf') 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. -# 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/.conf, which holds the colours under the scheme's own -# names, and palette/roles-.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 -- cgit v1.2.3