| 16 Feb 2026 |
 opeik | i think the nix shell shebangs are broken?
#!/usr/bin/env nix
#! nix shell nixpkgs#bash nixpkgs#hello nixpkgs#cowsay --command bash
hello | cowsay
outputs:
error: 'wat.sh' is not a recognised command
Try 'nix --help' for more information.
on:
✦ ❯ : nix --version
nix (Lix, like Nix) 2.93.3
System type: aarch64-darwin
Additional system types: x86_64-darwin
| 08:11:28 |
| opeik | * i think the nix shell shebangs are broken?
#!/usr/bin/env nix
#! nix shell nixpkgs#bash nixpkgs#hello nixpkgs#cowsay --command bash
hello | cowsay
outputs:
error: 'wat.sh' is not a recognised command
Try 'nix --help' for more information.
on:
✦ ❯ : nix --version
nix (Lix, like Nix) 2.93.3
System type: aarch64-darwin
Additional system types: x86_64-darwin
| 08:11:46 |
| opeik | * i think the nix shell shebangs are broken?
#!/usr/bin/env nix
#! nix shell nixpkgs#bash nixpkgs#hello nixpkgs#cowsay --command bash
hello | cowsay
outputs:
error: 'wat.sh' is not a recognised command
Try 'nix --help' for more information.
on:
❯ : nix --version
nix (Lix, like Nix) 2.93.3
System type: aarch64-darwin
Additional system types: x86_64-darwin
| 08:12:34 |
 holly [she/it] 🏳️⚧️ | i've seen discussion about this before, if i'm remembering correctly it's not implemented for nix3 cli in lix | 09:08:18 |
| opeik | darn, any reason why? it's very handy | 09:40:46 |
 Sofie 🏳️⚧️ (she/her) | this ^ | 10:05:13 |
 K900 | I think it's just that no one backported it from cppnix | 10:14:07 |
| K900 | And no one working on Lix wants to touch flake code that much | 10:14:18 |
 KFears 🏳️⚧️ (they/them) | I have attempted to backport it a while ago and it was a challenge. The code is not easy to understand, and I felt a lack of knowledge in both Lix and CppNix codebases to do it efficiently | 10:18:00 |
| K900 | I mean, there's a reason no one wants to touch the flake code :P | 10:18:54 |
| KFears 🏳️⚧️ (they/them) | Mhm, learned that firsthand | 10:19:31 |
| KFears 🏳️⚧️ (they/them) | (I also never knew how such shebangs are implemented, and this is a very specific amalgamation of checks that enables it, like I think the command needs to check its arguments and see how and where it's invoked and then manually read the next line of the file or something like that) | 10:21:06 |
| KFears 🏳️⚧️ (they/them) | (and I became kinda uncomfortable with doing this kind of feature in general, because of how special-case it is) | 10:21:35 |
| K900 | I mean honestly shebangs are just generally horribly cursed | 10:24:06 |
| 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 |
