I was having trouble installing (package! hyperbole), due to the following error during the nix-straight build:

       > ERROR: doom-emacs build resulted in files being written in $HOME of the build sandbox.
       > Contents of $HOME:
       > /build/tmp.9YIYoZ1pyj
       > /build/tmp.9YIYoZ1pyj/.hyperb

I solved this by, instead of using package!, adding pkgs.emacsPackages.hyperbole to the programs.doom-emacs.extraPackages list. No issues so far.

AFAIU, all I'm losing here are the configuration options of package! which I don't use and are mostly redundant anyway.

I'm thinking of similarly migrating all of my other package!s as well, as it should greatly simplify and reduce bugs in their installation; they will be built by one package (nix) manager instead of "3" (nix, nix-straight, nix-doom-emacs).

Is this a good idea? ckie (they/them) k0kada (he/him)

In reply to @hab25:matrix.org

I was having trouble installing (package! hyperbole), due to the following error during the nix-straight build:

       > ERROR: doom-emacs build resulted in files being written in $HOME of the build sandbox.
       > Contents of $HOME:
       > /build/tmp.9YIYoZ1pyj
       > /build/tmp.9YIYoZ1pyj/.hyperb

I solved this by, instead of using package!, adding pkgs.emacsPackages.hyperbole to the programs.doom-emacs.extraPackages list. No issues so far.

AFAIU, all I'm losing here are the configuration options of package! which I don't use and are mostly redundant anyway.

I'm thinking of similarly migrating all of my other package!s as well, as it should greatly simplify and reduce bugs in their installation; they will be built by one package (nix) manager instead of "3" (nix, nix-straight, nix-doom-emacs).

Is this a good idea? ckie (they/them) k0kada (he/him)

In reply to @hab25:matrix.org

I was having trouble installing (package! hyperbole), due to the following error during the nix-straight build:

       > ERROR: doom-emacs build resulted in files being written in $HOME of the build sandbox.
       > Contents of $HOME:
       > /build/tmp.9YIYoZ1pyj
       > /build/tmp.9YIYoZ1pyj/.hyperb

I solved this by, instead of using package!, adding pkgs.emacsPackages.hyperbole to the programs.doom-emacs.extraPackages list. No issues so far.

AFAIU, all I'm losing here are the configuration options of package! which I don't use and are mostly redundant anyway.

I'm thinking of similarly migrating all of my other package!s as well, as it should greatly simplify and reduce bugs in their installation; they will be built by one package (nix) manager instead of "3" (nix, nix-straight, nix-doom-emacs).

Is this a good idea? ckie (they/them) k0kada (he/him)

In reply to @hab25:matrix.org
I think it's a useful check, avoids hard to debug problems in the illegitimate cases. But what about directing users to prefer using extraPackages instead of `(package!)`, as I described?

But what about directing users to prefer using extraPackages instead of (package!), as I described?

A really bad idea because it will cause issues with NDE own code checks

But what about directing users to prefer using extraPackages instead of (package!), as I described?

A really bad idea because it will cause issues with NDE own code

But what about directing users to prefer using extraPackages instead of (package!), as I described?

A really bad idea because it will cause issues with doom-emacs own code

In reply to @k0kada:matrix.org

But what about directing users to prefer using extraPackages instead of (package!), as I described?

A really bad idea because it will cause issues with doom-emacs own code

In reply to @k0kada:matrix.org
No, but doom-emacs code is complex enough that I can imagine a few hard to debug issues to happen because you're not using the proper way to load a dependency

Hi all,

I'd like to be able to edit my config.el on the fly without having to rebuild (home-manager switch). I'm using the example home-manager configuration straight from README.md (with doomPrivateDir = ./doom.d;).

If I'm not mistaken, this actually used to work before, I didn't need to recompile. But it changed at some point.

Is this currently possible with nix-doom-emacs?

In reply to@ckie:ckie.dev
ribosomerocker: you probably want a (package! prop-menu)

In reply to @k0kada:matrix.org
But only ckie (they/them) can answer this question

When working on my config.el I usually test it out running emacs --load <path to config.el>

Of course this doesn't affect the emacs server.

In reply to @ckie:ckie.dev
extraPackages miiiight not get included in the nativecomp build

looks like it does. From M-x describe-function:

hyperbole-mode is an interactive and natively compiled function
defined in hyperbole.el.