| 20 Nov 2024 |
 just1602 | Linux Hackerman: oh yeah, I know it's not a lix problem, maybe I shouldn't have post here about it. It was more, damn compiling libreoffice didn't happen before.
But thanks for the info :)
| 20:37:32 |
| just1602 | nixpkgs is soo big, I try to go see the PR that fix the broken package and Github 500 in my face :( | 20:39:01 |
 szlend | Am I literally the only person who consistently gets annoyed by the lack of a null coalescing operator (or library function) in Nix/nixpkgs? I can't find any open issue about it :D | 21:20:02 |
| szlend | Or am I missing something really obvious | 21:20:13 |
 olivia | In reply to@szlend:matrix.org
Am I literally the only person who consistently gets annoyed by the lack of a null coalescing operator (or library function) in Nix/nixpkgs? I can't find any open issue about it :D nah I also want this | 21:30:10 |
| olivia | I think my preferred syntax would be or, and attrset.?attr would be equivalent to current attrset.attr or null | 21:31:23 |
| szlend | I swear I'm gonna add this to nixpkgs right now. What would we call it? lib.coalesce a b? Hopefully something shorter | 21:31:26 |
| olivia | but unfortunately that's a backwards incompatible change | 21:31:31 |
| szlend | I'd be happy with a lib function | 21:31:45 |
| olivia | yeah, same | 21:31:53 |
| olivia | In reply to@szlend:matrix.org
I swear I'm gonna add this to nixpkgs right now. What would we call it? lib.coalesce a b? Hopefully something shorter lib.<|> /s | 21:32:47 |
| szlend | lol | 21:33:07 |
| olivia | rust calls this .or (a method), haskell calls it <|>, js calls it ??, C calls it || (sorta) | 21:35:05 |
| olivia | none of these are usable as a library function here | 21:35:36 |
| szlend | there's already a lib.or though unfortunately. It could be lib.either but it kinda implies the same mechanics | 21:35:40 |
| szlend | though maybe not, just read the docs™ | 21:36:08 |
| szlend | I like the sound of lib.either a b | 21:36:24 |
| olivia | yeah that sounds reasonable to me | 21:36:42 |
| szlend | never thought I would be here complaining about a language being too strict about falseyness | 21:37:38 |
| olivia | lol | 21:37:57 |
| olivia | I'm very much happy with null-coalescing being a different operation from boolean-or | 21:38:16 |
| szlend | https://github.com/NixOS/nixpkgs/pull/357681 | 22:02:03 |
 Charles | I think the bikeshed should be called "coalesce" because I was immediately able to guess what it did because of the SQL thing of the same name | 22:52:21 |
| Charles | Maybe there should be a vote to determine whether there should be a vote to determine the name | 22:53:56 |
 bl1nk | Hey all, I finally switched over from nix to lix. I reused my existing home-manager configuration which includes some nix.settings. Now I see a lot of
warning: Ignoring the client-specified setting 'auto-optimise-store', because it is a restricted setting and you are not a trusted user
warning: Ignoring the client-specified setting 'log-lines', because it is a restricted setting and you are not a trusted user
warning: Ignoring the client-specified setting 'max-free', because it is a restricted setting and you are not a trusted user
warning: Ignoring the client-specified setting 'min-free', because it is a restricted setting and you are not a trusted user
when direnv'ing into my devshell. Did I break things, or is this expected because something changed? | 22:58:56 |
| bl1nk | In reply to@bl1nk:matrix.org
Hey all, I finally switched over from nix to lix. I reused my existing home-manager configuration which includes some nix.settings. Now I see a lot of
warning: Ignoring the client-specified setting 'auto-optimise-store', because it is a restricted setting and you are not a trusted user
warning: Ignoring the client-specified setting 'log-lines', because it is a restricted setting and you are not a trusted user
warning: Ignoring the client-specified setting 'max-free', because it is a restricted setting and you are not a trusted user
warning: Ignoring the client-specified setting 'min-free', because it is a restricted setting and you are not a trusted user
when direnv'ing into my devshell. Did I break things, or is this expected because something changed? I'm taking that back. It must have been some leftovers - works as expected now. | 23:09:03 |
| 21 Nov 2024 |
| szlend | I assume this just never worked and Nix silently swallowed it | 00:01:56 |
| szlend | auto-optimise-store, max-free, min-free are very much daemon settings and should preferably be set globally in /etc/nix/nix.conf. I wasn't even aware these could be passed down to the daemon from the client :D | 00:04:10 |
| szlend | alternatively you can set trusted-users = <your user> in /etc/nix/nix.conf like suggested | 00:04:48 |
|  Jost joined the room. | 00:09:44 |
