| 25 Jan 2026 |
 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 |
|  dadada changed their profile picture. | 20:33:50 |
| dadada changed their profile picture. | 20:38:54 |
| dadada changed their profile picture. | 21:17:31 |
| 26 Jan 2026 |
 neobrain | more annoyingly, apparently lix dot dev already ranks higher in bing/ddg search results than lix.systems despite being barely a week old :( | 07:54:50 |
| neobrain | * more annoyingly, apparently lix dot dev already ranks higher in bing/ddg search results for "lix documentation" than lix.systems despite being barely a week old :( | 07:55:00 |
| neobrain | (and the latter doesn't even come second but some web3 thing does) | 07:56:29 |
|  ollie changed their display name from nuv to ollie. | 08:35:13 |
 delroth | not yet here - but I mean, one has "lix documentation" in the title, the other doesn't and doesn't mention "documentation" anywhere on its landing page | 08:45:24 |
| delroth | (and to be clear, the one that has "lix documentation" in the title is not docs.lix.systems) | 08:46:39 |
 Sofie 🏳️⚧️ (she/her) | 
Download PXL_20260126_094121608.jpg | 09:41:44 |
| Sofie 🏳️⚧️ (she/her) | How would I know they actually succeeded? | 09:41:53 |
| Sofie 🏳️⚧️ (she/her) | Sorry for the bad picture btw ;3 | 09:43:19 |
| Sofie 🏳️⚧️ (she/her) | or is this too offtopic for this room again? 😭 | 09:43:39 |
