colonelpanic/dotfiles
1
0
Fork 1
Code Issues Pull Requests Packages Projects Releases Wiki Activity

picom: use absolute paths in @include directives

Browse Source 
The config files are symlinks to nix store, so relative paths don't
resolve correctly. Try using ~/.config/picom paths.

Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com>
This commit is contained in:
Ivan Malison
2026-02-01 13:41:24 -08:00
parent aacb4e5e99
commit 11cbe51ab8
1 changed files with 3 additions and 2 deletions
Download Patch File Download Diff File Expand all files Collapse all files

5
nixos/xmonad.nix
View File

@@ -208,11 +208,12 @@ makeEnable config "myModules.xmonad" true {
# Wrapper config that includes both home-manager generated config and animations # Wrapper config that includes both home-manager generated config and animations
# This works around picom not supporting multiple --config flags # This works around picom not supporting multiple --config flags
# Must use absolute paths since files are symlinks to nix store
xdg.configFile."picom/picom-with-animations.conf".text = '' xdg.configFile."picom/picom-with-animations.conf".text = ''
# Include home-manager generated base config # Include home-manager generated base config
@include "picom.conf" @include "~/.config/picom/picom.conf"
# Include spring physics animations (uses () list syntax) # Include spring physics animations (uses () list syntax)
@include "animations.conf" @include "~/.config/picom/animations.conf"
''; '';
# Override picom service to use our wrapper config # Override picom service to use our wrapper config