So apparently Nix can just, like, transparently fetch whatever thing you're trying to run if it isn't installed on your system yet. What
@joepie91 ok now to have a config that's just running the minimum commands that are dependent on everything you want installed (i'm 90% sure that's how nix does things more or less)
@teh_dude Ah, if you mean having everything you *actually* want installed as transitive dependencies, then that wouldn't work - NIX_AUTO_RUN uses nix-shell, which is ephemeral, so the dependencies don't get installed to your global system environment (plus the bin/ etc. wouldn't be exposed in PATH for transitive dependencies anyway)
@joepie91 Let's see if I will regret putting that in my session variables ^^
@joepie91 
I'm not sure I like that...
@schmittlauch It's surprisingly safely implemented - if there are multiple packages offering the same binary name then it'll make you choose one first, and it only fetches packages from nixpkgs, which has at least had nominal review :)
(So basically, it avoids the two biggest security issues that eg. npx has)
@joepie91 woah