fix(hyprlua): deploy Vicinae theme where Vicinae actually scans for it
The config-copy step put cyberqueer.toml into ~/.config/vicinae/, but Vicinae loads NAMED custom themes only from ~/.local/share/vicinae/themes/*.toml (per the official docs). So settings.json's theme.dark.name="cyberqueer" never resolved and the launcher silently fell back to the stock dark theme. Copy the theme into ~/.local/share/vicinae/themes/ so the named theme resolves and the cyberqueer palette is applied. Note: the hyprland and niri DE modules have separate, pre-existing Vicinae layout issues (hyprland double-nests settings.json; niri bundles no vicinae config) — left for a dedicated follow-up. Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01R5kHioUMK3mtf2eiLEozCMmain
parent
4332abde35
commit
734e28b1fc
|
|
@ -341,6 +341,15 @@ for cfg in "${CONFIGS[@]}"; do
|
|||
cp -r ~/Dotfiles/desktopenvs/hyprlua/"$cfg" ~/.config/
|
||||
done
|
||||
|
||||
# Vicinae loads NAMED custom themes from ~/.local/share/vicinae/themes/*.toml —
|
||||
# NOT from ~/.config/vicinae/. The cyberqueer.toml copied above (into
|
||||
# ~/.config/vicinae/) is therefore never found, so settings.json's
|
||||
# theme.dark.name="cyberqueer" silently falls back to the stock dark theme.
|
||||
# Deploy the theme into the location Vicinae actually scans so it resolves.
|
||||
mkdir -p ~/.local/share/vicinae/themes
|
||||
cp -f ~/Dotfiles/desktopenvs/hyprlua/vicinae/cyberqueer.toml \
|
||||
~/.local/share/vicinae/themes/cyberqueer.toml
|
||||
|
||||
# In hyprlua, device-specific overrides (monitors, keybinds, autostart, etc.)
|
||||
# live inside ~/.config/hypr/usr/ as Lua modules loaded by hyprland.lua via
|
||||
# require("usr.*"). The usr/ directory is already bundled inside the hypr/
|
||||
|
|
|
|||
Loading…
Reference in New Issue