| 25 Feb 2024 |
 danielsidhion | If you want to use an existing section, "trivial build helpers" is probably the best one to put it in. If we were to create a new section, what sort of things would you like to group together with it (so we can figure out a better section name)? | 11:27:57 |
 Lurkki | Not sure about grouping, since I'm unfamiliar with most of pkgs/build-support | 12:14:35 |
| 26 Feb 2024 |
 infinisil | Shahar "Dawn" Or (mightyiam): Could you consider changing the name from eelco to something else? It doesn't feel right to use a person's name as a project name in general, but especially if that person is very well-known in the community already. | 20:06:28 |
| infinisil | * Shahar "Dawn" Or (mightyiam): Could you consider changing the name from eelco (also via nix.dev) to something else? It doesn't feel right to use a person's name as a project name in general, but especially if that person is very well-known in the community already. | 20:08:07 |
| 27 Feb 2024 |
 @mightyiam:matrix.org | If Eelco is not offended then we're golden, aren't we? | 00:00:32 |
| infinisil | Shahar "Dawn" Or (mightyiam): That's definitely a requirement, but that wouldn't make it a better choice | 01:26:04 |
| infinisil | It leads to cases like if you say "I'd like to introduce <name>", you'd have to explain that it's actually some_thing_, not the person that everybody knows already.
Or if somebody says "Have you tried <name>?" it sounds really weird if somebody isn't aware that the project <name> is a thing | 01:28:26 |
 asymmetric | i personally just find it a bit in poor taste.. seems unnecessary targeting of an individual with a joke that might make them (or other people) feel uncomfortable, for imho no apparent gain | 09:00:23 |
 @jade_:matrix.org | In reply to @mightyiam:matrix.org
If Eelco is not offended then we're golden, aren't we? the minute i even mentioned it i had to clarify because it's incredibly confusing | 09:05:20 |
 @dooy:matrix.org | If it helps I was confused and wondered if Eelco is in Thailand | 13:39:19 |
|  trinity changed their display name from chococandy to trinity. | 14:20:35 |
| infinisil | Johannes Kirschbauer @hsjobeki: Do you want write access to nixdoc? It's probably not necessary, but I'd be happy to add you, since your PR was very high quality :) | 19:02:25 |
| 28 Feb 2024 |
 @johannes.kirschbauer:scs.ems.host | In reply to @infinisil:matrix.org
Johannes Kirschbauer @hsjobeki: Do you want write access to nixdoc? It's probably not necessary, but I'd be happy to add you, since your PR was very high quality :) Maybe yes. I think this could help speed up the rfc migration. | 10:27:14 |
|  kranurag7 removed their profile picture. | 10:54:59 |
| 29 Feb 2024 |
 i97henka | Sorry, no doc meeting for me this afternoon - some family stuff to attend to. I still very much want to be part of the team. | 13:15:23 |
| @johannes.kirschbauer:scs.ems.host | Is the doc team aware that docs for lib.fixedPoints.composeExtension are broken in unstable?
https://nixos.org/manual/nixpkgs/unstable/#function-library-example-lib.fixedPoints.extends
(I cannot directly link to it anymore) | 14:03:21 |
| @johannes.kirschbauer:scs.ems.host | * Is the doc team aware that docs for lib.fixedPoints.composeExtension are broken in unstable?
https://nixos.org/manual/nixpkgs/unstable/#function-library-example-lib.fixedPoints.extends
(I cannot directly link to it anymore, because rendering broke) | 14:03:41 |
| @johannes.kirschbauer:scs.ems.host | * Is the doc team aware that docs for lib.fixedPoints.composeExtension and the following items there are broken in unstable?
https://nixos.org/manual/nixpkgs/unstable/#function-library-example-lib.fixedPoints.extends
(I cannot directly link to it anymore, because rendering broke) | 14:05:15 |
| danielsidhion | I wasn't aware of that. Looks like some tech debt saying hello 🥲
On the devmode server things look fine, which is what I think most folks use to check the result of their writing | 14:21:07 |
| danielsidhion | I created a PR to fix it. Docs team meeting is soon, so I'll make sure we go over it https://github.com/NixOS/nixpkgs/pull/292340 | 14:26:49 |
| @johannes.kirschbauer:scs.ems.host | It seems those kind of problems can be avoided when we migrate to commonmark. I guess the problem was that we used fenced divs ::: inside an example, which uses a different rendering that the rest of the comment. | 14:30:14 |
| danielsidhion | Yeah, it's likely the code thought the note was part of the examples. As you said, after the migration this kind of thing shouldn't happen anymore | 14:32:25 |
| infinisil | In reply to @infinisil:matrix.org
Shahar "Dawn" Or (mightyiam): Could you consider changing the name from eelco (also via nix.dev) to something else? It doesn't feel right to use a person's name as a project name in general, but especially if that person is very well-known in the community already. https://github.com/mobusoperandi/eelco/issues/100 | 16:29:15 |
| 1 Mar 2024 |
| infinisil | In reply to @johannes.kirschbauer:scs.ems.host
Maybe yes. I think this could help speed up the rfc migration. Just gave you access. I'd still like to review PRs, but if I'm not responsive or you think it's not worth reviewing feel free to merge yourself :) | 03:07:37 |
| @johannes.kirschbauer:scs.ems.host | just having fun today: using "nix#nix-clangStdenv" i get sigSEV (segmentation fault). But using "nix#nix" is fine no segfault.
I just dont understand whats the difference in this convoluted flake.nix file in the cpp nix repository. | 11:25:43 |
| @johannes.kirschbauer:scs.ems.host | * just having fun today: using "nix#nix-clangStdenv" i get SIGSEGV (Address boundary error). But using "nix#nix" is fine.. no segfault.
I just dont understand whats the difference in this convoluted flake.nix file in the cpp nix repository. | 11:26:27 |
| @johannes.kirschbauer:scs.ems.host | * just having fun today: using "nix#nix-clangStdenv" i get SIGSEGV (Address boundary error). But using "nix#nix" is fine.. no segfault.
I just dont understand whats the difference in this convoluted flake.nix file in the cpp nix repository.
Apart from that i would expect either both or none of the outputs to have segfaults. | 11:27:02 |
| @johannes.kirschbauer:scs.ems.host | * just having fun today: using "nix#nix-clangStdenv" i get SIGSEGV (Address boundary error). But using "nix#nix" is fine.. no segfault.
I just dont understand whats the difference in this convoluted flake.nix file in the cpp nix repository.
Apart from that i would expect either both or none of the outputs to have segfault. | 11:27:13 |
| @johannes.kirschbauer:scs.ems.host | Some background, currently i patch nix before using it. It seems my patch spontaneously produces segfaults with clangStdenv only. | 11:29:38 |
| @johannes.kirschbauer:scs.ems.host | * Some background, currently i use a patched nix. It seems my patch spontaneously produces segfaults with clangStdenv only. | 11:30:02 |
