| 21 Mar 2025 |
 joepie91 🏳️🌈 | ... okay, so that doesn't look like a syntactic restriction to me at all, just a typecheck on a value | 17:08:21 |
| joepie91 🏳️🌈 | in which case my complaint doesn't apply as stated | 17:08:56 |
 elikoga | No this is a syntactic check. With flake.nix: import ./why.nix and why.nix: {} we get
elikoga@hpLaptop:~/Dev/thymis/why-are-we-having-this-discussion]$ nix eval flake.nix
warning: Path '/home/elikoga/Dev/thymis/why-are-we-having-this-discussion/flake.nix' should point at the directory containing the 'flake.nix' file, not the file itself. Pretending that you meant '/home/elikoga/Dev/thymis/why-are-we-having-this-discussion'
error:
… while evaluating the file '/nix/store/q3vbzdgg0r1hdxki9zc2aqap78nl9qj8-source/flake.nix':
error: file '/nix/store/q3vbzdgg0r1hdxki9zc2aqap78nl9qj8-source/flake.nix' must be an attribute set
Which tells us that this is not "just a typecheck on a value"
| 17:10:17 |
| elikoga | I think in the case that one can do eta-expansion, one may want to loosen the restriction (assume the user does not destructure the args) | 17:11:23 |
| joepie91 🏳️🌈 | in which case my complaint does apply | 17:12:38 |
| joepie91 🏳️🌈 | . | 17:12:51 |
| joepie91 🏳️🌈 | it doesn't matter that you can technically still evaluate flake.nix via Nix directly and have it evaluate, because that has no bearing on how people actually use flake.nix files. what matters is that people cannot use "the way they write Nix files" for a flake.nix and expect it to work for its intended purpose, namely via nix flake evaluation | 17:13:39 |
| joepie91 🏳️🌈 | because, with additional syntactic restrictions, it is not actually the same format | 17:14:04 |
| joepie91 🏳️🌈 | if it were, you would be able to have a flake.nix that's just import ./actual-flake.nix where actual-flake.nix contains a valid flake | 17:14:26 |
| joepie91 🏳️🌈 | * if it were, you would be able to have a flake.nix that's just import ./actual-flake.nix where actual-flake.nix contains a valid flake (after all, the evaluated value would be identical) | 17:16:37 |
| elikoga | 
Download hqdefault.jpg | 17:18:05 |
| joepie91 🏳️🌈 | okay, I guess this is where I stop bothering to put effort into an explanation then. | 17:18:39 |
| joepie91 🏳️🌈 | you do you. | 17:18:48 |
| 22 Mar 2025 |
 hexa | https://github.com/NixOS/nix/issues/4945 fwiw | 00:31:08 |
|  isabel joined the room. | 00:42:31 |
|  vaw joined the room. | 21:25:44 |
| 23 Mar 2025 |
|  @sincetheflood:matrix.org left the room. | 00:21:10 |
| 24 Mar 2025 |
|  @eisfunke:eisfunke.com changed their display name from Nicolas Lenz to Nicolas. | 13:39:58 |
| 25 Mar 2025 |
|  @dminca:matrix.org joined the room. | 21:58:40 |
| 26 Mar 2025 |
|  EVA-01 changed their profile picture. | 03:50:55 |
| EVA-01 changed their profile picture. | 19:29:10 |
| 28 Mar 2025 |
|  ester 🐇 changed their display name from uakci to ester 🐇. | 08:07:40 |
|  Daniel joined the room. | 13:48:38 |
|  Rayane Nakib (ريّان نقيب) changed their display name from Rayane Nakib (ريان نقيب) to Rayane Nakib (ريّان نقيب). | 22:51:51 |
| 30 Mar 2025 |
|  woile joined the room. | 16:33:39 |
| woile | hi everyone, I was hoping someone could explain how nixConfig works in a flake. I've seen it in ghostty terminal's flake, and so I thought I would add the nix-community to my flake, which uses fenix. My understanding is that I would add the server for the binary cache, is this correct? But when I run nix develop and I'm thrown into a shell, I get the warning:
ignoring the client-specified setting 'trusted-public-keys', because it is a restricted setting and you are not a trusted user
| 19:03:42 |
| 31 Mar 2025 |
|  evolve joined the room. | 08:46:48 |
| 1 Apr 2025 |
|  Zhenxing He joined the room. | 03:24:14 |
|  @3wy-kra:matrix.uni-hannover.de left the room. | 09:35:48 |
|  zapotecorum joined the room. | 10:02:15 |
