| 24 Jan 2026 |
|  innocentzer0 joined the room. | 01:13:21 |
|  holly [she/it] 🏳️⚧️ changed their profile picture. | 09:08:06 |
 Acid Bong | In reply to @milo:wiro.world
lix fmt doesn't behave the same as nix fmt when invoked with no arguments.
nix fmt passes the project root directory (the one parent of the flake.nix) as the default argument.
Whereas, lix fmt simply acts as a nix run .#formatter.
Is this intentional? If so, what is the reason? If not, could I volunteer a PR to match nix's behaviour?
what's lix fmt? is there a lix-fmt executable? | 09:39:47 |
 neindochoh! / Seti (they/them) | Lix 2.92 introduced a breaking change in the behaviour of the fmt command: https://docs.lix.systems/manual/lix/2.94/release-notes/rl-2.92.html?highlight=fmt#breaking-changes | 09:46:19 |
| neindochoh! / Seti (they/them) | * | 09:48:05 |
| Acid Bong | In reply to @milo:wiro.world
lix fmt doesn't behave the same as nix fmt when invoked with no arguments.
nix fmt passes the project root directory (the one parent of the flake.nix) as the default argument.
Whereas, lix fmt simply acts as a nix run .#formatter.
Is this intentional? If so, what is the reason? If not, could I volunteer a PR to match nix's behaviour?
btw, what are Lix and Nix versions you're having? | 09:54:35 |
 niko ⚡️ | In reply to @milo:wiro.world
lix fmt doesn't behave the same as nix fmt when invoked with no arguments.
nix fmt passes the project root directory (the one parent of the flake.nix) as the default argument.
Whereas, lix fmt simply acts as a nix run .#formatter.
Is this intentional? If so, what is the reason? If not, could I volunteer a PR to match nix's behaviour?
I believe nix changed that behavior like a year ago at this point | 11:19:50 |
| niko ⚡️ | There’s been numerous warnings about that behavior changing soon at least | 11:20:06 |
| niko ⚡️ | This is also why it’s advised to use nixfmt-tree for the formatter output | 11:20:26 |
| 13 May 2024 |
|  zrsk joined the room. | 13:37:30 |
|  dariof4 joined the room. | 14:16:05 |
|  abbe joined the room. | 14:42:22 |
 mjm | lix is now in nixos-unstable, what's the best way to use it in a NixOS config? | 15:47:41 |
 K900 | nix.package = pkgs.lix | 15:47:54 |
| K900 | Probably | 15:47:58 |
| K900 | Or just keep using the module | 15:48:02 |
 puck | you can use nix.package = pkgs.lix; if you want; but using the overlay will guarantee more updates (tho less binary cache) | 15:48:44 |
| mjm | well, the module/overlay doesn't easily support using the one from nixpkgs | 15:48:44 |
| mjm | i do want more binary cache | 15:49:21 |
| mjm | yeah i guess i'll just do nix.package then | 15:50:43 |
 raitobezarius | to have binary cache and HEAD, we will probably need to track the channels and bolt a lix on there and rebuild with our own CI then push in our binary cache | 17:33:17 |
 Charles | What's lix using as its binary cache? Attic? | 17:34:36 |
|  Arian left the room. | 17:37:44 |
 @tc424:glasgow.social | Last I heard they were using garage as the back end, and think about attic | 17:39:11 |
| @tc424:glasgow.social | I don't know if that means they're just pushing directly into garage's s3 interface for the moment | 17:39:36 |
| @tc424:glasgow.social | * Last I heard they were using garage as the back end, and thinking about attic | 17:39:57 |
| raitobezarius | In reply to @charles:computer.surgery
What's lix using as its binary cache? Attic? garage without attic | 17:41:16 |
| raitobezarius | it's homemade just nix push thingie | 17:41:24 |
| raitobezarius | and nix sign | 17:41:25 |
 Qyriad | yep | 17:44:26 |
