| 6 Aug 2025 |
| @bestlem:matrix.org joined the room. | 20:02:33 |
| 8 Aug 2025 |
| 0x4A6F joined the room. | 07:02:20 |
| 14 Sep 2025 |
| Emma [it/its] joined the room. | 08:39:50 |
| 15 Sep 2025 |
| @bestlem:matrix.org left the room. | 10:22:07 |
| 18 Sep 2025 |
Niclas Overby Ⓝ |  Download image.png | 10:21:01 |
Niclas Overby Ⓝ | Hi accelbread ! Have you considered supporting something like this in Flakelight, so that input overlays can be moved to the withOverlays folder? | 10:22:56 |
Niclas Overby Ⓝ | And actually the same for lib, so you can use pkgs in lib | 10:25:48 |
Niclas Overby Ⓝ | * And actually the same for lib, so you can use pkgs in the lib folder | 10:27:02 |
accelbread | that should already work, right? | 14:36:21 |
Niclas Overby Ⓝ | It seems to cause an infinite recursion | 14:39:24 |
Niclas Overby Ⓝ |  Download image.png | 14:39:26 |
accelbread | Ah, I see. I'll take a look | 14:41:40 |
accelbread | interestingly, something like the following in nix/withOverlays/default.nix works:
final: prev: (prev.lib.composeManyExtensions [
prev.inputs.nixgl.overlays.default
prev.inputs.emacs-overlay.overlays.package
prev.inputs.self.overlays.overrides
prev.inputs.self.overlays.lix
]) final prev
So computing the module arguments is triggering evaluation of withOverlays... hmm
| 15:10:09 |
Niclas Overby Ⓝ | Does it make sense that this is supported?: (How does Flakelight know whether it is an overlay or a function to setup multiple overlays, like in my example ?)
withOverlays = overlay;
Shouldn't it only support?:
withOverlays = [overlay, ...];
| 15:18:28 |