| 25 Jan 2026 |
 toonn | The advice would still apply. Don't get them in advance. | 11:34:15 |
 KFears (they/them) | In reply to @kfiz:matrix.sopado.de
Is this currently (going to be) supported in lix? https://nix.dev/manual/nix/2.22/command-ref/new-cli/nix3-shell#use-as-a--interpreter That might have been backported by me a year back, but I'm not fully sure. If it wasn't, it was because maintaining that functionality would be hard | 11:34:25 |
| KFears (they/them) | In any case, I would advice to test if it works | 11:35:07 |
 jappie | belgian rail is going on a strike this week (25th - 30th, including both of these days), though usually they're pretty good at only listing trains that actual run in the route planner (website / app)
https://www.belgiantrain.be/en/travel-info/train-network-travel-info/strike | 11:35:20 |
 delroth | this is getting very off-topic but this is wrong advice for basically anyone who doesn't already live in belgium - ICEs have early bird pricing, eurostar/thalys does too, etc. | 11:35:48 |
| delroth | * this is getting very off-topic but this is wrong advice for basically anyone who isn't already in belgium - ICEs have early bird pricing, eurostar/thalys does too, etc. | 11:36:10 |
| delroth | (ECD from NL might too? not sure) | 11:37:12 |
| delroth | I'm happy I'm not going to FOSDEM this year :p | 11:37:54 |
| delroth | though that probably wouldn't impact the routes I'd take (through Köln or through Paris) | 11:38:11 |
 QuadRadical (Ping) @ FOSDEM | Even the Eurostar is somewhat affected, some trains have been cancelled or delayed | 11:40:20 |
| QuadRadical (Ping) @ FOSDEM | So it might also affect going through Paris etc | 11:40:28 |
| QuadRadical (Ping) @ FOSDEM | * Even the Eurostar from London is somewhat affected, some trains have been cancelled or delayed | 11:40:36 |
| delroth | oof | 11:57:50 |
 Arian | Meh Belgian rail system on strike is probably still more organized than German rail system on a normal day | 12:18:30 |
 neobrain | Given a flake with multiple checks, how does one actually run one specific check? nix flake check seems to unconditionally run them all | 13:05:56 |
 Psentee | I think you can address them like packages or other outputs, nix flake check '.#check_name', but it's been a while since I used flakes so I might be wrong | 13:07:03 |
| neobrain | nope, error: unexpected fragment 'nixosSystemAcceptsLib' in flake reference '.#nixosSystemAcceptsLib' | 13:07:40 |
 Unhooked Spirits | I think it's "nix build .#system.checks.name" | 13:08:00 |
| Unhooked Spirits | But you have to know the system | 13:08:07 |
| 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 |
