| 9 Aug 2023 |
 JoelMcCracken | yeah | 19:58:12 |
 mei 🌒& | so that's about where i timed out last time after running around the room trying to read elisp | 19:58:40 |
 j4m3s | slighty related question, is it sufficient to lock doom's git version to lock package version or ? (I'm confused about the ~/.emacs.d/bin/doom upgrade | 19:59:10 |
| mei 🌒& | moooostly | 19:59:28 |
| mei 🌒& | all of doom's own packages should be pinned, but the user doesn't have to specify a pin | 19:59:50 |
| mei 🌒& | like I have all of these: | 20:00:09 |
| mei 🌒& | 
Download image.png | 20:00:10 |
| j4m3s | Yeah right, i was just confused by the fact that in the modules they're called w/o the pin | 20:00:41 |
| j4m3s | But seems like the pin is global to the repo :) | 20:00:49 |
| mei 🌒& | 
Download image.png | 20:01:36 |
| mei 🌒& | JoelMcCracken: so this is another thing to consider actually. we need to save straight's resolutions. or every package registry's, but that might not be as feasible | 20:02:42 |
| mei 🌒& | i'm tending more towards that doom2nix that saves all the source url/commit-ish/hash pins | 20:03:43 |
| j4m3s | mb then, I remembered it being empty. Thanks for the correction ~ | 20:07:46 |
| JoelMcCracken | what is doom2nix? | 21:15:16 |
| JoelMcCracken | also,
we need to save straight's resolutions
is this covered by e..g exporting them as json output?
| 21:16:07 |
| JoelMcCracken | * also,
we need to save straight's resolutions
is this covered by e..g exporting them as json output?
| 21:16:16 |
| mei 🌒& | JoelMcCracken: it's a thing that doesn't exist. but it'd be a CLI that pokes the network and creates a nde-specific json lockfile for resolutions | 21:20:29 |
| mei 🌒& | the idea is we want to put as little as possible behind the hash-dependent part with the network access | 21:21:08 |
| JoelMcCracken | hmm | 21:29:12 |
| 10 Aug 2023 |
| JoelMcCracken | I imagine I could add some shim here https://github.com/nix-community/nix-straight.el/blob/master/setup.el#L20 | 03:07:07 |
| JoelMcCracken | iterate over al of the nix-straight--packages and then use straight-recipes-retrieve to access the info for each | 03:09:21 |
| 11 Aug 2023 |
| JoelMcCracken | is there a way to develop like a test suite for nix-straight.el? | 03:33:45 |
| JoelMcCracken | i see an example in nix-doom-emacs | 04:33:07 |
| mei 🌒& | JoelMcCracken: i have this tree with straight moved into the nde repo | 12:53:09 |
| mei 🌒& | https://github.com/ckiee/nix-doom-emacs/commits/move-nix-straight-in | 12:53:10 |
| JoelMcCracken | ah | 19:01:16 |
| JoelMcCracken | yeah that may be easier | 19:01:28 |
| 13 Aug 2023 |
|  @10leej:matrix.org joined the room. | 01:25:19 |
| JoelMcCracken | Do you think this is the right direction to go? I don't know why nix-straight was originally made a separete package | 03:01:25 |
| mei 🌒& | JoelMcCracken: idk either, NDE is older than my maintenance of it | 13:36:34 |
