| 3 Jan 2026 |
|  Tanja (she/her) changed their display name from Tanja (she/her) - ☎️ 4201 to Tanja (she/her). | 19:15:05 |
|  Hrushikesh joined the room. | 20:43:15 |
| 4 Jan 2026 |
|  Find me at aleksana:qaq.li changed their display name from aleksana 🏳️⚧️ (force me to bed after 18:00 UTC) to aleksana 🏳️⚧️ (deprecated). | 17:12:54 |
| Find me at aleksana:qaq.li changed their display name from aleksana 🏳️⚧️ (deprecated) to Find me at aleksana:qaq.li. | 17:14:40 |
| 5 Jan 2026 |
|  kybe joined the room. | 04:02:42 |
|  Kleha joined the room. | 06:07:51 |
|  Laura A joined the room. | 08:56:59 |
|  @twig6943:matrix.org left the room. | 23:17:36 |
| 8 Jan 2026 |
|  pltrz set a profile picture. | 23:50:13 |
| 9 Jan 2026 |
| pltrz changed their profile picture. | 00:00:44 |
|  xoartox joined the room. | 18:52:07 |
| 11 Jan 2026 |
|  ghpzin changed their display name from ghpzin (moved to @ghpzin:envs.net) to ghpzin. | 15:04:32 |
|  @ghpzin:envs.net left the room. | 16:21:53 |
| 12 Jan 2026 |
|  @sbc64:matrix.org left the room. | 16:15:15 |
 Ilan Joselevich (Kranzes) | Is there a place explaining NIX_PATH parsing with more complex paths like "nixpkgs=flake:github:NixOS/nixpkgs/nixos-22.05" which include many colons? | 17:08:25 |
| Ilan Joselevich (Kranzes) | I'm trying to implement the full NIX_PATH parsing logic in snix but I dont even understand the behavior in Nix. | 17:09:17 |
| Ilan Joselevich (Kranzes) | Could someone write a NIX_PATH string that includes all the 5 search path attrsets in this example? https://nix.dev/manual/nix/2.33/language/builtins#builtins-findFile | 17:11:33 |
| Ilan Joselevich (Kranzes) | (If that's even possible?) | 17:11:56 |
 SomeoneSerge (back on matrix) | In reply to @kranzes:matrix.org
(If that's even possible?) Looking at the code, it's not; -I only works because it skips parseNixPath or something | 17:16:32 |
| SomeoneSerge (back on matrix) | But nix path parsing is already stateful, so you could make a backwards incompatible change to accommodate those? | 17:18:07 |
 Sergei Zimmerman (xokdvium) | In reply to @ss:someonex.net
But nix path parsing is already stateful, so you could make a backwards incompatible change to accommodate those? Greedy behaviour here would have been nice, but from my discussion with raito that’s not exactly a priority atm | 17:39:42 |
| Sergei Zimmerman (xokdvium) | Valentin had a meme for this | 17:40:23 |
| Sergei Zimmerman (xokdvium) | 
Download ima_fc5f740.jpeg | 17:42:23 |
 raitobezarius | it would be ideal to find a path forward to destroy NIX_PATH parsing | 18:15:16 |
| raitobezarius | especially due to the meme | 18:15:24 |
| Ilan Joselevich (Kranzes) | https://gist.github.com/Kranzes/da0ee0920adf9ce94183b6cec3bbe9c2 | 18:24:28 |
 roberth | I think a lot of folks share that sentiment, on a spectrum between discourage and destroy. What would you suggest for a solution? | 18:24:30 |
| Ilan Joselevich (Kranzes) | FWIW: That search path is taken from the docs of findFile, makes it a whole lot more confusing when you realize it works with -I but not with NIX_PATH | 18:25:12 |
| raitobezarius | There's not much solutions to propose at this step | 18:25:26 |
| raitobezarius | It depends on a rework of the setting system | 18:25:32 |
