| 15 May 2024 |
 @jade_:matrix.org | this should get release noted. theres so much "we just fixed some shit" that should get release noted | 21:58:33 |
 julia | oh actually I suspect now why it might have been failing, on our nixos-infected systems the version of nix in use is the weird one with leftover statw that's several versions old.... | 21:59:14 |
 Qyriad | In reply to @jade_:matrix.org
this should get release noted. theres so much "we just fixed some shit" that should get release noted Yeah we::Qyriad only recently realized "oh wait these bugs were user facing they should probably get release notes…" | 21:59:31 |
| @jade_:matrix.org | btw a sneak peek of upcoming CLs: https://docs.lix.systems/manual/nightly/release-notes/rl-next.html | 21:59:59 |
| @jade_:matrix.org | i finally fixed this one | 22:00:08 |
| julia | :o | 22:01:44 |
 FireFly | In reply to @jade_:matrix.org
do you mean my nixcon 2023 talk ;-) I was thinking more a guide to the directory structure and where some important building blocks are located in the nixpkgs tree, but how to find where things are defined is also very helpful :D (and lix :doc helps a lot here, so thanks for that ^^) | 22:09:22 |
| @jade_:matrix.org | the lix :doc was 4 years in the making ;; | 22:09:37 |
| @jade_:matrix.org | i still can't believe we made it happen | 22:09:45 |
| Qyriad | I'm so fucking glad we did | 22:09:54 |
| FireFly | on a related note I reported a very minor bug to the upstream nix-doc repo the other day (and one attempt at addressing it, though it's possible there's better ways to do it--my rust-fu isn't very strong yet) | 22:10:17 |
| Qyriad | Now we just need to put docstrings on every lambda in all of Nixpkgs :^) | 22:10:18 |
| FireFly | (though maybe it should've gone to the lix repo? idk, I figure since it applies to the upstream one as well..) | 22:10:48 |
| @jade_:matrix.org | In reply to @firefly:raccoon.college
(though maybe it should've gone to the lix repo? idk, I figure since it applies to the upstream one as well..) needs ports to both if it affects both | 22:11:07 |
| @jade_:matrix.org | oh wow i completely missed the PR emails or something I think | 22:11:41 |
| FireFly | yeah it's just that a line **foo:** gets its leading asterisk chomped, which leads to it appearing italic and with a trailing asterisk when rendered | 22:11:44 |
| @jade_:matrix.org | i have been leaking inbox items like a sieve | 22:11:49 |
| FireFly | as I said, very minro :p | 22:11:51 |
| FireFly | * as I said, very minor :p | 22:11:55 |
| FireFly | and my fix was just checking if there's whitespace after the #/* when cleaning up a single line | 22:12:31 |
| Qyriad | omg I totally forgot that we made this. We need to like. put this somewhere probably https://mermaid.live/edit#pako:eNp9lN1u2yAUx18Fsds4CbHjr3aVNrWTdrFNWnu1eRfYJjExYAfwV6NIe5o92J5k2GkTN03HlTnnz_-cH2B2MClSAkNoWVYkNNWMhOAhI4DRFUm6hBFQrECJkxyviQJUgK-0jcSgjsSKFU2SYanBw20kgBkm-4kyon5G8BDox7XSshDrG5MEd20piVK0ENezp_BI2DczmiudElFPeX5LJK2xNqvADpQCcwLeg3fbqtBXRUmEUuwwuQI1kb35MW1P51NkP2f__v6zH5WbjepF8NdLBGBZ4K7GrDrUtawbcGrjg9ZSEX0Rc9Tsk-yIeh3L2ZhXYV7e7MAlIOtl57orT5L0WGEMZqr0dmc4r3ruuT4LpbE57hPavS4kOWkvgg2akeH_sWaCtkZglswaWy0yJsoFl1J16SJ-dDlVyJ4jlbpsE1svmaeprC_DnHU5dP6dYEbVMD-IRoGe9b6KlbnY1XHBt0qXlVYXxR8ryszummtKklcrLm7KU-7SbR4RPI_Rpgi_fSzFpmkCumWZlwU85W7e2ize5iVezs82xYqpeNOLN9Rxg7qs7bnoqLtJy_XGrVO5XnLZijo490pJ_aYX6my5CnjdLjORxpvcKZMaZ9kW-65AnRSvvIrkTa9YBqrL_azO7db3cBNsVb1JeJyu8LqZb7tzL47fZmR513buijnMdmI7a5DvCBR4DW7VnC9ceuY1_s3PrxKcQE4kxzQ1L9-uT0RQZ4STCIbmM8Uy7496b3S40sV9JxIYalmRCazKFGtyS_FaYg7DFWbKREssYLiDLQxt5E2R4zvIW869BXKc5QR2MPScqeP4yLF95HsOQsF-Ah-LwjigCSQpNYRfDg_x8B4Pjj-G_FBh_w93i87u | 22:15:56 |
| FireFly | ohh that's good | 22:17:44 |
| Qyriad | I do feel like it's still missing something | 22:18:25 |
| Qyriad | But I'm not sure what | 22:18:33 |
| FireFly | though I wonder if the "realisation" box should be styled like evaluation/instantiation? (but ye not sure how to deal with the "can happen either through substitution or building the derivation" in that case..) | 22:18:47 |
| Qyriad | (Well, besides an a paragraph of text to actually accompany it) | 22:18:50 |
| Qyriad | In reply to@firefly:raccoon.college
though I wonder if the "realisation" box should be styled like evaluation/instantiation? (but ye not sure how to deal with the "can happen either through substitution or building the derivation" in that case..) Yeah I'm not sure how to communicate that substitution and builder execution are the two methods of realisation | 22:19:40 |
| FireFly | maybe two separate vertical lines from Store Derivation to Outputs, and writing the names of the phases off to the side? | 22:20:43 |
| FireFly | or maybe that'd be more confusing, not sure | 22:20:57 |
| FireFly | or well writing the "Realisation" off to the side next to the two lines, idk if my mental image translates over text | 22:21:30 |
