<mcwitt>
Hi, I'm hitting an issue on using hm as a nix-darwin module where 'config.home.profileDirectory' is defaulting to '/var/empty/.nix-profile', though the profile is installed to '~/.nix-profile' as I expected (causing modules that refer to profileDirectory to break). Wondering if it's a known issue or I'm missing something obvious?
joesventek has quit [Quit: Quit]
joesventek has joined #home-manager
mcwitt` has joined #home-manager
mcwitt` has left #home-manager [#home-manager]
mcwitt has quit [Ping timeout: 260 seconds]
mcwitt`` has joined #home-manager
mcwitt`` has quit [Ping timeout: 258 seconds]
rajivr has quit [Quit: Connection closed for inactivity]
<piegames>
Now that the default value for `home.user` was removed, how can I add it back again? I want to deploy my configuration for multiple users and I can't (easily) if I must hard-code the username.
* piegames
doesn't fully understand the motivation for that change tbh
<ronthecookie>
figured out what was up with home.sessionPath - need to use an actual login shell for .profile to get sourced
<rycee>
piegames: You can add `home.user = builtins.getEnv "USER"` to your configuration to recover the previous behavior.
<piegames>
rycee: That's easy, thanks.
<piegames>
Any reason why this was changed beyond "it's impure"? Any caveats, edge cases?
<ronthecookie>
rycee im guessing its unintended that hm-session-vars.sh doesnt run if you don't login into a shell? i use a display manager so the first shell that runs is my term
<ronthecookie>
fun, writing that out loud makes it sound kinda stupid
<rycee>
piegames: It was a bad idea to have it in HM since it is super brittle, especially if you are deploying your configuration to a target with a different username than the one you use when deploying.
<piegames>
ronthecookie: You need to source it in `/etc/profiles` (or whatever your graphical setup sources when logging you in)
<ronthecookie>
one would think that'd be done for me as since on nixos
<ronthecookie>
as i'm*
<rycee>
ronthecookie: Try putting it into `~/.xprofile`.
<piegames>
rycee: Yeah, just thought of that as well. I'll remember to don't do those for now, but I don't think there is a solution that solves both problems :/
<rycee>
ronthecookie: If you use HM to manage your X session then it will put it in `~/.xprofile`.
<ronthecookie>
i think i am, leeme check
<ronthecookie>
lol, i use the nixos xserver and home manager to configure i3
<ronthecookie>
how that works is beyond me, anyway that explains that oddity
<ronthecookie>
thanks
<ronthecookie>
rycee: i'm still a bit confused, do i keep nixos services.xserver enabled or does HM handle it all? im not sure where the border is
<piegames>
ronthecookie: The border is: is it per user or system wide? system services are system wide --> NixOS config
<piegames>
Those services usually look for configuration in the current user's $HOME by default. Thus, you can (partially) configure them using home-manager.
<ronthecookie>
well the login/display manager is system wide but then it doesnt run another X session for the user...right?
<rycee>
ronthecookie: My system configuration is more or less:
<ronthecookie>
i guess cleaner but it's longer and i'm probably gonna get rid of the DM soon enough, just wanted to get it working for now but neat
<ronthecookie>
anyway it works now, thanks!
<rycee>
ronthecookie: Cool. glad it turned out OK :-)
* ronthecookie
is doing this at ~1am
<ronthecookie>
i3 seems to determine the starting workspace with the first workspace keybind it finds and its in the right order here but once HM does its thing it seems to get sorted