max / alloy

Seed a shop config from the theme, both polarities

Author: Max Johnson <me@maxj.phd> · 2026-07-31 15:14 UTC

Signed with PGP, not checked

Commit: 86830df69864f7622714fe410fc92e49a3847a4e

Parent: 0f6420a

1 file changed, +27 insertions, -0 deletions

A templates/etc/skel/.config/shop/config.toml.in +27

		@@ -1,0 +1,27 @@
1	+	@{! variants = default, night }
2	+	# Alloy shop configuration — @{meta.name}
3	+	#
4	+	# shop is the terminal Alloy is moving to; rio is what the image installs
5	+	# today, and docs/STACK.md still documents rio as the pick. So this file seeds
6	+	# a config for a shop the user brings themselves, and is in place for the swap.
7	+	# Both configs render from the same theme, so the two terminals cannot disagree
8	+	# about a colour while both exist.
9	+	#
10	+	# This template carries no colour, which is the whole difference from rio's
11	+	# `[colors]` block. shop takes a makeover theme by id and resolves the
12	+	# sixteen ANSI slots itself, through the same `makeover::ansi_intent` table the
13	+	# kernel cmdline and setvtrgb render from. So the palette cannot drift out of
14	+	# step here the way sixteen transcribed hex values could: there is nothing to
15	+	# transcribe.
16	+
17	+	# The theme, by id. `alloy theme apply` swaps this file for its `.night`
18	+	# sibling, which is the same template rendered against the other polarity, so
19	+	# switching the desktop switches the terminal.
20	+	theme = "@{meta.id}"
21	+
22	+	# Alloy's own theme directory, searched ahead of shop's packaged and embedded
23	+	# tiers. shop ships makeover's embedded copies of both Akari themes and would
24	+	# come up themed without this line; it is here so a machine-local edit to
25	+	# /usr/share/alloy/themes reaches the terminal, and so a theme that only Alloy
26	+	# ships resolves at all.
27	+	themes = "/usr/share/alloy/themes"