<evanjs>
trace: warning: The option `programs.bash.enableAutojump' defined in `/home/evanjs/src/nixos_cfg/config/new-modules/console/console-hm.nix' and `/home/evanjs/src/nixos_cfg/config/machines/non_nixos/wgrig/home.nix' has been renamed to `programs.autojump.enableBashIntegration'.
<evanjs>
that is satisfying lol
<evanjs>
I take it detailed "reason" messages are not required in most cases?
joesventek has quit [Quit: Quit]
joesventek has joined #home-manager
Jezhehim[m] has joined #home-manager
joesventek has quit [Quit: Quit]
joesventek has joined #home-manager
<evanjs>
rycee: #1503 -- well that only took a day (incl not working on it and probably sleeping less than I should lol)
<evanjs>
Doing better at including outstanding questions in PRs rather than asking before they're committed. Nobody likes meta-questions lol
<evanjs>
Seems to work on my system :D yay zsh autojump
<evanjs>
mmmm was going to add myself to maintainers+codeowners for numlock, but now I'm wondering... if a module's sole option is enabling a related service, should the module itself be better placed under "modules/services"?
<evanjs>
Currently, numlock is under "modules/misc"
<evanjs>
Or does that more depend on the attribute itself? e.g. services.xxx would go under services, whereas xsession.numlock would not
kenran has quit [Ping timeout: 240 seconds]
cole-h has joined #home-manager
dermetfan has quit [Ping timeout: 244 seconds]
johnw has joined #home-manager
kenran has joined #home-manager
kenran has quit [Ping timeout: 256 seconds]
__monty__ has joined #home-manager
s1341 has quit [Quit: Connection closed for inactivity]
<rycee>
evanjs: Not sure, the intention might be that the module isn't so much about running numlockx as it is about turning on the numlock key in the X session.
<evanjs>
rycee: yeah that's what I was thinking
kenran has joined #home-manager
kenran has quit [Ping timeout: 265 seconds]
<drakonis>
wow topic change!
__monty__ has quit [Quit: leaving]
tdeo has quit [Read error: Connection reset by peer]