With any of the packages, you can always use override to set specific things like withNativeComp.

So you could do, e.g:

pkgs.emacs29.override {
    withNativeComp = true;
}

IIRC, it defaults to enabling native comp when the package is not being cross-compiled?

In reply to @mattsturg:matrix.org

Sorry if this isn't the right place, but I figured I'd ask here first:

I use a gnome wayland session, usually with the dark theme. When I run nix run nixpkgs#emacs-gtk3 I get an xwayland window with a correctly themed dark titlebar, however when I run nix run nixpkgs#emacs-gtk3 I get a native wayland window, but the titlebar is always drawn using the light theme.

Why is that, and is there a way to tell emacs to respect the light/dark desktop theme? Or at the very least explicitly set the titlebar to be dark?

Interestingly, when I use auto-dark-emacs the mode is correctly detecting changes in light/dark theme and applying that to emac's colorscheme, but the frame's titlebar remains stuck on the light theme.

Looking online, it seems others have had a similar issue when using xorg and/or xwayland, but their solutions usually involve using xprop to set _GTK_THEME_VARIANT. This won't help me on pgtk+wayland 🙁

I still haven't solved this btw.

I'm guessing pgtk on Wayland uses client side decorations while the xwayland "legacy" gtk build is using server side decorations.

Is there a way to tell Emacs to use dark/light theme for the decorations?

Looking in frame properties, I found undecorated which I could use to remove all decorations (assuming pgtk supports that), ns-appearance is used to configure dark/light mode but only works on macos 😭

Also ns-transparent-titlebar, again Darwin exclusive, allows setting decorations to match emac's background colour.

:b emacsPackages.trivialBuild {
                  pname = "consult-omni";
                  version = "2024-09-26";
          
                  src = pkgs.fetchFromGitHub {
                    owner = "armindarvish";
                    repo = "consult-omni";
                    rev = "87b5bcf0e55c01e6a4a24ae74ce691f55d1455a2";
                    hash = "sha256-x5rNTNEDLoHzIlA1y+VsQ+Y0Pa1QXbybt2rIUBJ+VtM=";
                  };
          packageRequires = with emacsPackages;[ embark consult ];
          files = ''("*.el" "sources/*")'';
                }

In reply to @elfahor:matrix.org
Hey, I'm trying to figure out which emacs package to install. In nixpkgs, there are packages emacs30, emacs29, and emacsNativeComp, with the latter being Emacs 28. I'm using Doom Emacs so I can't yet use emacs30. Doom Emacs recommends Emacs 29 + native comp, and I can't figure out whether emacs29 has native compilation...

In reply to @cf11:0x2c.org
You'll want to join the doom emacs discord as that is where it's community hangs out and provides support.

In reply to @yisraeldov:matrix.org
Hi all, I'm thinking of making the switch to Doom. It seems to have many sane defaults and I end up copying most of what they have anyway into my own commit. Is there a recomended way to use doom on nix ?

I use two methods which can be selected for each host with an option:

1. On my main laptop where I may make more frequent edits to my emacs config I let doom/emacs handle its own dependencies. I roughly follow the config from the doom developer.
2. On other systems where I'm not regularly changing my config I use doom-nix-unstraightened, which essentially handles as much as possible through nix. This pulls my doom config from github, so a commit+push+nix update is then needed for any change to take effect. OTOH I can run my emacs config on a new system in a fully automated way and updates to my system also update doom and emacs packages. I've also had one emacs package want to create files in its install location at runtime which fails when that's the nix store (which is annoying).