9e2667f8fe
Saving a theme stopped sticking: the choice was captured only by the fish `kitten` wrapper, so `kitty +kitten themes`, a keybinding or any non-fish shell wrote <appearance>-theme.auto.conf directly and the next regeneration overwrote it from theme-modes. The dark slot had already lost a pick that way -- dark-theme.auto.conf held #0d0f31 while canonical dark said #2b2c2e. Move the capture into apply-theme-mode.sh, which every path runs. It records a cksum of each generated file after the repair step; on the next run a file whose checksum differs was written by something else, so it becomes canonical for that appearance. With no state recorded yet nothing is adopted, so a first run cannot mistake a pinned mode's duplicated files for real choices. The fish wrapper keeps only its useful part: re-apply the mode and reload so the change shows at once. theme-modes/dark.conf is the recovered #0d0f31 (1984). Covered by a new case in tests/test_theme_mode.sh that writes the theme file with no shell involved. |
||
|---|---|---|
| .. | ||
| private_tests | ||
| theme-modes | ||
| themes | ||
| kitty.app.icns | ||
| kitty.conf | ||
| private_current-theme.conf | ||
| private_executable_apply-theme-mode.sh | ||
| private_executable_repair-auto-themes.sh | ||
| symlink_theme.conf.tmpl | ||
| tab_bar.py | ||