Eelco Dolstra
Eelco Dolstra
Thanks, I've used your merge commit. The fallthrough warning looks like it could be an upstream PR?
Yeah I've run into this as well. Haven't investigated it closely yet.
Hm, not sure I understand the problem description. `nix develop` already support multi-line strings, e.g. in Nix's own flake: ``` $ nix develop $ echo "$shellHook" PATH=$prefix/bin:$PATH unset PYTHONPATH export...
See #10612 for the motivation why this is the case (in short: the `narHash` doesn't guarantee that we have all the other attributes that the fetcher might return, like `lastModified`...
I don't really get the motivation for this change (another massive refactoring PR, which I assume will be followed by an even bigger change when this gets applied to the...
SSH can already do this, see the `ServerAliveInterval` and `TCPKeepAlive` options in `ssh_config`.
The attribute name should include "nixos" to distinguish it from other types of configurations (e.g. home-manager configurations). Maybe `nixosConfigurationsFor.`? However, I'm not really convinced that this is needed. Unlike (say)...
:+1: on changing `` to `«code»`.
Duplicate of #1902.
A few ideas: * Let's lower the severity of the warning for unrecognized flake outputs. Currently you can have arbitrary flake outputs, but `nix flake check` warns about them, which...