Silvan Mosberger

> Returning a canonical path may not always be feasible. > > Would a `builtins.readLink` function be sufficient for the purpose of filesets? Yes that would be sufficient (should be...

Unfortunately the PR fixing it for Nixpkgs/NixOS won't fix it for the Nix Pills :/ So I think we should still leave this open for now

Fwiw, in the latest version, the output is this: ```nix { single = [ "a" ]; short = [ "a" "b" "c" ]; long = [ "a very very" "long...

We [previously decided](https://github.com/NixOS/nixfmt/pull/57#issuecomment-2135872189) to deprecate the directory mode of `nixfmt` and instead encourage [treefmt](https://github.com/numtide/treefmt), for which I recently [implemented parallel formatting](https://github.com/numtide/treefmt/pull/282). So I don't think there's anything to do here,...

I think we can close this actually, because we now [deprecated recursive mode](https://github.com/NixOS/nixfmt/pull/240), and are recommending treefmt instead, which does run in parallel.

My theory is that it works on my mailserver because I happen to use `mail.infinisil.com` subdomain. But in absence of the standard `mail.` subdomain, the autodiscovery DNS records as described...

Discussed this in todays meeting ```nix { currentStyle = [ "hello" "beautiful" ] ++ lib.optionals true [ (x ++ [ bash ]) "wonderful" "world" ]; proposal1 = [ "hello" "beautiful"...

> Btw., I did not know there was a high-bandwidth synchronous discussion for this. It'd be great if such meetings that meaningfully discuss an issue could be announced before-hand in...

Since the agenda is flexible, you can influence it by just joining the meeting and letting us know the issues you think are important so we can discuss them right...

Discussed together in the meeting: - Proposal 2 better after all as @emilazy suggested? - @infinisil, @0x4A6F, @Sereja313: Yeah - @dasj: Not used to it, but wouldn't be very sad...