826a9417e7
theme-mode is a per-machine preference, and the three *-theme.auto.conf files are generated from it plus themes/, so tracking any of them made every machine flag the others' choice. Drop all four from the source state and ignore them. That leaves a freshly applied machine with no theme files for kitty to read, so add run_after_kitty-theme-mode.sh to regenerate them from the canonical themes. It defaults to `auto`, so a new machine follows its OS until told otherwise, and it exits quietly where this kitty config isn't applied rather than failing the run. Since that script now runs on every apply, including on Linux, make the permission lookup in both shell scripts fall back from BSD `stat -f` to GNU `stat -c` and then to 600. |
||
|---|---|---|
| .. | ||
| private_tests | ||
| 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 | ||