Mei Schoenberg
Mei Schoenberg
You could probably do something like this: ```lisp ;(this probably won't run, but that's an exercise for the reader as I haven't tried this) (advice-add 'doom/reload :before (lambda (&rest r)...
Try this: ```patch From 99b749e1c5e6d061b376d789c1756ce9b3241ad0 Mon Sep 17 00:00:00 2001 From: ckie Date: Fri, 10 Jun 2022 17:50:53 +0300 Subject: [PATCH] home/doom-emacs: maybe fix nix-community/nix-doom-emacs#141 --- home/doom-emacs/default.nix | 3 ++-...
Sounds like runtime dependencies, so you could add something like this to the arguments you're passing into nix-doom-emacs: ```nix extraConfig = '' (setq exec-path (append exec-path '( ${ concatMapStringsSep "...
I'll gladly merge the `native-comp-deferred-compilation-deny-list` patch if it's submitted as a PR, eventually.
Yeah, the `doom` CLI doesn't work yet. I only recently added it to the final binary and I started writing a fix but it's still sitting somewhere in my local...
Fair, as you wish :P
https://github.com/nix-community/nix-doom-emacs/actions/runs/6502685395/job/17662123038#step:5:188
We probably missed some nativecomp and it's doing that in the "background" trying to catch up. But yup, broken.
I think there's no need. There's just a bunch of things that should be done at build that aren't, this issue can stay open as another note of that.
@leifhelm: Yes, except Doom is the one calling `straight-use-package` and it does have the pin info. It's just a lot of unfun specialized Elisp hacking to figure out the details.