<piegames>
Simply put `assertions = [{ assertion = false; message = "Task failed successfully"; }];` in a few random places and see if it still builds
andi- has quit [Ping timeout: 258 seconds]
andi- has joined #home-manager
psiquo has joined #home-manager
thibm_ has quit [Ping timeout: 246 seconds]
rajivr has quit [Quit: Connection closed for inactivity]
spaark has joined #home-manager
<spaark>
not sure if this is the best place, but i have a question about configuring xmonad. if i have a custom module i want to use, do i just manually place it in ~/.xmonad/lib/, or is there a better way to do it with home-manager?
<__monty__>
Do you have a cabal file?
<spaark>
__monty__: just a .hs file
psiquo has quit [Quit: psiquo]
<__monty__>
Then I'm lost I thought you had to edit code to configure XMonad? So I assume there's that code. And then there's *also* the code for the custom lib.
<spaark>
there is a primary config file (xmonad looks for ~/.xmonad/xmonad.hs), but i've also create a separate .hs file just so i can modularise my code.
<spaark>
xmonad looks for these extra modules in ~/.xmonad/lib/, but i was wondering if home-manager could take the files i give it and put it in that folder for me.
<spaark>
i could look into adding that functionality if it's not there, albeit my nix knowledge is lacking
<__monty__>
Looks like you should pass it as `xsession.windowManager.xmonad.extraPackages`. But that would mean you need to package it.
<__monty__>
You could try an activation block that puts the file in place.
<spaark>
what's an activation block?
<__monty__>
Hmm, or maybe `home.file.".xmonad/lib/myfile.hs" = ~/myfile.hs` works.
<__monty__>
And if that doesn't work you might need an activation block.
<spaark>
__monty__: ah, setting it that way worked! it's a nice solution.
<spaark>
only difference is i had to append '.source'. home.file.(...).source = ./myfile.hs