Killer feature ! Thanks
sorry, i just updated for the first time after 2 months (this is the amount of time it took for me to untangle the many nests of my configā¦), and the first thing i see is:
error: The option `users.users.USER.maid.kconfig' was accessed but has no value defined. Try setting the option.
do i have to set it for nix-maid to work now? even though i dont use KDE at all?
EDIT: oh, it compiles if i just put a dummy option:
users.users.USER.maid.kconfig.settings = { };
interestingly, without .settings it still doesnt work�
EDIT2: since then i migrated to hjem with hjem-rum as i did not receive any support here twice :)
What a good idea!
Itās not obvious to me how to know what options KDE makes available - Iāve tried a web search and the best documentation I can find is src/kwin.kcfg Ā· master Ā· Plasma / KWin Ā· GitLab , which (I think?) is not complete.
I agree. This was just the minimum piece of integration get the ball rolling. My idea to improve the situation of discoverability is twofold:
- Add some high-level modules, probably keeping the same API as plasma-manager.
- Write a new
kconfig-declarative watchcommand, that on a similar way todconf watch /would print the changes you make to KDE.
(For now Iāve just been querying my LLM of choice about which file/option does what, which is surprisingly accurateā¦)