Daiderd Jordan

@lloeki By default the nix client evaluates using the system it was built with. So upgrading you nix installation to the arm build will also change the default.

For me there are 2 important things that are a priority for the project. - **safety**: Unlike NixOS system configuration here has to live next to the existing operating system....

Since it's a recurring topic in the comments, I think moving the repo is somewhat beside the point. There could be reasons to do so in the future but for...

This comes from `programs.zsh.promptInit`, you can can put a custom prompt snippet there or explicitly not configure anything. ```nix { programs.zsh.promptInit = ""; } ```

The same thing happens for all shells so I'm not sure what the issue is.

I'm not a fish user so I don't know what to look for but I'd take a look at https://github.com/NixOS/nixpkgs/pull/45784. Also verifying the following might help to narrow down the...

If that also works for the version of fish in 18.09 something similar could be added to the module by default.

It's related to #140, multiple paths are added for compatibility with both the single and multi-user install. But nix complains if one of the defined search paths does not exist.

It was the same at some point, but things got out of sync over time.

That depends on what the actual trigger for that problem is. Unlike that case most service users like this should have a homedir, which might result in the problem not...