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

picom: disable home-manager settings generation entirely

Browse Source 
Set settings = {} to prevent home-manager from generating any picom
config settings that would be appended to our custom config file.
This was causing duplicate/conflicting settings.

Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com>
This commit is contained in:
Ivan Malison
2026-02-02 12:39:40 -08:00
parent 8045c4cc9d
commit f22a96e37b
1 changed files with 4 additions and 4 deletions
Download Patch File Download Diff File Expand all files Collapse all files

8
nixos/xmonad.nix
View File

@@ -92,12 +92,12 @@ makeEnable config "myModules.xmonad" true {
enable = true; enable = true;
}; };
# Disable home-manager's picom config generation - we'll write a complete config # Enable picom service but disable its config generation - we write our own config
# ourselves to work around the libconfig list vs array syntax issue # to work around the libconfig list vs array syntax issue for animations
services.picom = { services.picom = {
enable = true; enable = true;
vSync = config.myModules.xmonad.picom.vSync.enable; # Don't let home-manager generate any settings - we handle everything in xdg.configFile
backend = "glx"; settings = {};
}; };
# Write complete picom config directly to avoid home-manager's libconfig generator # Write complete picom config directly to avoid home-manager's libconfig generator