From a06d8f948c4d5a60bff992c3d6f26b5fb54f80cb Mon Sep 17 00:00:00 2001 From: "Danilo M." Date: Mon, 28 Sep 2026 12:41:10 +0200 Subject: docs(terminal): current-theme.conf is a symlink into kitty-conf The README still called it a real file. It now links into the kitty-conf repository and install.sh writes the theme through it (47dcb72). Co-Authored-By: Claude Opus 5.5 --- templates/terminal/README.md | 7 +++++-- 1 file changed, 5 insertions(+), 2 deletions(-) diff --git a/templates/terminal/README.md b/templates/terminal/README.md index 3c2bda6..b7246e9 100644 --- a/templates/terminal/README.md +++ b/templates/terminal/README.md @@ -11,8 +11,11 @@ rather than accidental ones. ## What changed -- `~/.config/kitty/current-theme.conf` was a symlink into `~/.cache/wal/`. It - is now a real file holding the upstream `catppuccin/kitty` macchiato theme. +- `~/.config/kitty/current-theme.conf` was a symlink into `~/.cache/wal/`, so + pywal owned the terminal palette. It is now a symlink into the separate + `kitty-conf` repository, and `install.sh` writes the generated theme through + that link rather than replacing it, so the theme content is tracked in + `kitty-conf`. - `~/bin/wal.sh` no longer recreates that symlink. It did so on every wallpaper change, which would have silently reverted the theme. - Neovim used `colorscheme pywal`, reading the same pywal output. It now uses -- cgit v1.2.3