<energizer>
what causes .zprofile to be sourced in a noninteractive nonlogin shell?
<energizer>
er no that doesn't happen
<energizer>
how does nix get on my PATH for `ssh foo 'echo $PATH'`?
<immae>
energizer: it executes your zsh shell which then runs the command. Like `zsh -c "echo $PATH"`, plus other argument (probably -l or the "-zsh" usual hack). Non-interactive zsh doesn’t source .zprofile (see man zshall it details precisely what files it sources in what situation)
<energizer>
immae: that's what i'm wondering about. i can `ssh my-nixos 'echo $PATH'` and nix stuff will be shown on PATH
<energizer>
but i dont know how it got there
<energizer>
and nix isn't on path with my non-nixos home-manager system
<energizer>
in non-interactive non-login ssh
<immae>
energizer: other files get loaded
<immae>
/etc/zshenv for instance
<energizer>
immae: empty
<__monty__>
Afaict non-interactive login zsh still reads zprofile and zlogin.
<immae>
__monty__: the doc says it doesn’t load zprofile
<immae>
(but it does load zlogin)
<immae>
energizer: you should look at the doc it says precisely which files are read
<energizer>
ssh foo echo isn't a login shell
<__monty__>
Then that's probably right.
<immae>
It is energizer
<immae>
it’s not an interactive shell but it’s a login one
<immae>
you may also have variables set via pam environment (look at /etc/pam.d/login if you have a pam_env.so conffile=/nix/store/somehash-pam-environment)
<energizer>
/etc/pam.d/login has some stuff but nothing that looks related
<immae>
/etc/pam.d/sshd maybe? (look for pam_env.so)
<immae>
the module is called security.pam, I’m not sure what’s your point here? If you want to point that you didn’t define anything, it’s normal, they’re default values
<energizer>
how can i see what the default values of system.build.pamEnvironment are?
<energizer>
aha, i can look in the repl
<cole-h>
Is there a way to specify a nixpkgs path for home-manager to use? I want my system on unstable, but I want to run my user account and its packages from master.
<energizer>
thanks immae
<immae>
you’re welcome
<immae>
cole-h: only way is to set the variable before invocation: `NIX_PATH=nixpkgs=another-path home-manager ...`
<cole-h>
Well, I'm planning on using hm through the NixOS module
<immae>
ah sorry I missed that bit
<immae>
Then I have no clue sorry
<immae>
:q
<immae>
(oups cursor went outside of vim)
<cole-h>
My next question is: how do I get ~/.config/nixpkgs/overlays to apply for the NixOS module?
<energizer>
cole-h: man home-configuration.nix talks about that under nixpkgs.overlays
<energizer>
(won't necessarily answer your question but it might help)