From 2b200e92a9ebd57d6b78826372975677e660d44c Mon Sep 17 00:00:00 2001 From: Craig Jennings Date: Tue, 27 Jan 2026 18:13:57 -0600 Subject: docs(todo): add task to review theme config architecture The dunst/fuzzel configs exist in both dotfiles/common (stowed) and dotfiles/hyprland/.config/themes/ (templates), requiring edits in multiple places. Needs a cleaner single-source-of-truth approach. Co-Authored-By: Claude Opus 4.5 --- todo.org | 11 +++++++++++ 1 file changed, 11 insertions(+) diff --git a/todo.org b/todo.org index bb71ce8..c90bb1f 100644 --- a/todo.org +++ b/todo.org @@ -137,6 +137,17 @@ Also, the text is quite large. For consistency, we should make it the same size Fuzzel menu border blends in too much. Change border color to blue or red to make the menu more visible when it appears. +**** TODO [#C] Review theme config architecture for dunst/fuzzel +The active dunst config is stowed from dotfiles/common/ but theme templates +live in dotfiles/hyprland/.config/themes/. set-theme copies the templates to +the stowed locations at runtime, so edits to the common file get overwritten +on theme switch. This split between stowed configs and theme templates is +error-prone — changes must be made in both places. Consider: +- Having set-theme be the single source of truth (remove common dunstrc from stow) +- Or symlinking the stowed config to a theme-managed location +- Same situation applies to fuzzel.ini +The goal is a single place to edit each config, not two. + **** TODO [#D] Consider Customizing Hyprland Animations Current: windows pop in, scratchpads slide from bottom. -- cgit v1.2.3