| 25 Jan 2026 |
 neobrain | Ah yeah that works, thanks! I tried without system.checks before and then it tried to go through pkgs instead :D | 13:09:28 |
 kfiz | Just tested. Doesn't work for me with this:
#! /usr/bin/env nix
#! nix shell nixpkgs#bash nixpkgs#hello nixpkgs#cowsay --command bash
hello | cowsay
| 13:59:37 |
| kfiz | Interesting. How do you run your scripts? | 14:01:00 |
| kfiz | * 0x4fbb09 it/its ⛯✇ΘΔ: Interesting. How do you run your scripts? | 14:01:33 |
 0x4fbb09 it/its ⛯✇ΘΔ | oh wait did i confuse 2 features together, i have
#!/usr/bin/env nix-shell
#!nix-shell -i fish -p fish validator-nu ripgrep
| 14:05:56 |
| 0x4fbb09 it/its ⛯✇ΘΔ | which runs the rest of the shell in fish, with validator-nu and ripgrep in PATH | 14:06:11 |
| 0x4fbb09 it/its ⛯✇ΘΔ | right, i did, that's not the same thing | 14:06:42 |
| 0x4fbb09 it/its ⛯✇ΘΔ | well i think it is, but just the older cli. in practice that's the same | 14:07:23 |
 KFears (they/them) | There are gotchas between the old CLI and new CLI, and also in the shebang invocation thing... | 14:11:45 |
| KFears (they/them) | Last I checked, the impl was pretty horrifying, like it was an if gate in the CLI command code that checked if this is invocation from the shebang with means I don't remember, and then it like, parsed the next line as the command invocation but with a few special variables set which modified behavior, and then ran the rest | 14:14:00 |
| KFears (they/them) | And the code had like, ifs nested 4 layers deep, and also it was written in the nix-build command code, because apparently nix-shell isn't a separate command, but instead nix-build code switches between different modes with a bunch of flags based on whether the argv0 is nix-build or nix-shell, and otherwise they use the same function for impl which is like 400 lines long and has ifs nested 4 layers deep | 14:15:58 |
| KFears (they/them) | I previously thought old CLI salvageable, but this was one of the two reasons I gave up on the idea of improving it to get somewhere good | 14:17:25 |
| KFears (they/them) | The second reason was nix-env | 14:17:31 |
| KFears (they/them) | In reply to @kfears:matrix.org
And the code had like, ifs nested 4 layers deep, and also it was written in the nix-build command code, because apparently nix-shell isn't a separate command, but instead nix-build code switches between different modes with a bunch of flags based on whether the argv0 is nix-build or nix-shell, and otherwise they use the same function for impl which is like 400 lines long and has ifs nested 4 layers deep Err it might not be the nix-build file and command that is used for nix-shell, but nix-env file and command | 14:18:23 |
| KFears (they/them) | I don't quite remember | 14:18:29 |
 isabel | seeing the nix.dev link i thought ohh it would be cool to make lix.dev but thats taken by a ai thing 😭 | 14:36:16 |
| 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 |
