| 7 Sep 2023 |
 ckie (they/them) | vaguely. not sure if that's precisely the right one | 13:57:45 |
| ckie (they/them) | yeah this isn't the right one | 14:00:01 |
| ckie (they/them) | I think I was thinking of [RFC 0092] Computed derivations but it's been >a year, need to reread | 14:02:38 |
 JoelMcCracken | yeah i don't know | 14:03:33 |
| JoelMcCracken | i imagine it would work like:
- a user picks a package to install from a list
- nix installs it
- emacs loads it within the running process
| 14:05:37 |
| ckie (they/them) | mhm, it's essentially tearing out the parts of straight&emacs that do network I/O into their own emacs, running inside a nix build | 14:06:42 |
| ckie (they/them) | which works happily for the top-level imperative emacs usecase (editing your config before rebuilding) but you want to have all of these prefetched in the build process once you're ready to deploy it to your 'prod' machine | 14:07:22 |
| ckie (they/them) | recursive nix isn't actually a hard dependency-- we can crudely and inefficiently emulate it, but it would make this much more streamlined since it would run through approximately the same codepath in both imperative/Nix sandbox | 14:08:44 |
| ckie (they/them) | * recursive nix isn't actually a hard dependency-- we can crudely and inefficiently emulate it, but it would make this much more streamlined since it would run through approximately the same codepath in both the imperative/Nix sandbox usecases | 14:08:49 |
| JoelMcCracken | yeah | 14:08:55 |
| JoelMcCracken | well it depends, what you mean specifically by recursive nix i guess | 14:09:27 |
