Jonas Chevalier

yeah agreed, this issue is not solved

When we wrote the rule my impression was that the space was predominant. We should adopt whatever style is predominant in nixpkgs.

> Does that mean you prefer adopting predominant style over good/useful style? It depends on how clear the improvement is. For example, here it could make things less consistent: ```nix...

I'm fine having this in nixpkgs-fmt, we just need somebody to send in a PR. It would also be nice to have that as part of the Nix language as...

This is going to be solved by adding nixpkgs-fmt as a pre-commit hook to nixpkgs.

I think the next step would be to open a [RFC](https://github.com/NixOS/rfcs) to get more community feedback. 1. Release rnix-fmt 2. Get it integrated in nixpkgs somehow, either through GitHub Actions...

Related issue: https://github.com/rust-analyzer/smol_str/issues/25

I don't think it's the same issue. The previous one was that formatting the code twice would not give the same result. This seems to be an issue with the...

Or maybe it should add `\n` after the `=`: ```nix let nix = if !buildNix then null else buildRacketNix; in { } ```

I agree that the current re-formatting is not ideal.