| 30 Nov 2025 |
 Aijokey | Redacted or Malformed Event | 18:18:41 |
| Aijokey | Download configuration.nix | 18:18:51 |
| Aijokey | I need diffrent matrix client maybe | 18:19:20 |
 Blastboom Strice | Did you try putting it like this:
```nix
Text
``` | 18:20:48 |
| Aijokey | I'm not good with matrix or markdown(?) | 18:21:38 |
| Blastboom Strice | (Its a mix of both, cuz matrix clients use markdown, but might use slightly different implementations) | 18:22:15 |
 @acidbong:envs.net | code blocks are the same, only lists, newlines and single `mono phrases` vary | 18:23:58 |
| @acidbong:envs.net | anyway
do pipe operator implementations vary between Nix and Lix? i'm using Nix for everything on my system, but build my NixOS with Lix just for the sake of multiline output, and I don't wanna mess up with my (and/or someone else's) code | 18:26:08 |
 WeetHet | I think the behaviour should be somewhat the same but the feature names are different | 18:26:59 |
| @acidbong:envs.net | aha, Lix has no <| | 18:32:30 |
 piegames | In reply to @acidbong:envs.net
anyway
do pipe operator implementations vary between Nix and Lix? i'm using Nix for everything on my system, but build my NixOS with Lix just for the sake of multiline output, and I don't wanna mess up with my (and/or someone else's) code Only in operator precedence, but this should be of little to no practical relevance | 18:32:50 |
|  @rainbowcat:xmr.se left the room. | 18:36:53 |
| @acidbong:envs.net | understandable, i guess i'll abstain from it (lib.pipe is already familiar for me) | 18:44:11 |
 raitobezarius | In reply to @weethet:catgirl.cloud
Also I thought that both flakes and nix3 CLI were gonna be moved to a separate module? Not nix3 CLI | 18:47:01 |
| raitobezarius | Flakes yes | 18:47:04 |
| raitobezarius | It's going to be very very progressive | 18:47:12 |
| raitobezarius | (and yes this means that plugins will gain the ability to extend the REPL) | 18:49:52 |
| raitobezarius | (or the nix3 CLI itself) | 18:50:03 |
| WeetHet | How would nix3 cli function without flakes? | 18:53:41 |
 niklaskorz | if you specify a file with -f it works on normal nix files instead of flakes | 19:02:06 |
| WeetHet | Yeah but nix3 cli with -f is just strictly worse than nix2 cli? | 19:02:34 |
| niklaskorz | well that wasn't your question | 19:03:14 |
| niklaskorz | I too prefer nix-build when working with normal files :D | 19:03:49 |
| WeetHet | What's the point in leaving nix3 CLI in Lix if it would be there strictly so that an external plugin would work | 19:04:00 |
| niklaskorz | (or nom-build, for that matter) | 19:04:04 |
| niklaskorz | there are some more or less agreed upon improvements to be made I think, like defaulting to default.nix if no flake.nix is found (or if no flake plugin is enabled I suppose) | 19:05:11 |
| niklaskorz | and then interpreting the list of installables as attributes, so nix build foobar would be equivalent to nix-build -A foobar | 19:06:05 |
| WeetHet | What is the advantage to doing that instead of just working with nix2 cli? | 19:06:36 |
| WeetHet | * What is the advantage in doing that instead of just working with nix2 cli? | 19:07:27 |
 just1602 | Having a unified CLI? | 19:12:16 |
