I'm OK with keeping it in staging-next as a compromise (it comes earlier to master than staging). The last eval already contains the change due to getting merges from master. https://hydra.nixos.org/jobset/nixpkgs/staging-next

@ckiee mentioned that doom-emacs still doesn't work with emacs29 for some reason. I'd prefer to hold off on dropping emacs28 until next release.

ckiee mentioned that doom-emacs still doesn't work with emacs29

To be clear, it is nix-doom-emacs, not doom emacs.

As far as I remember the doom issue affects all Emacs, not merely the newer ones.

As far as I remember the [nix-doom-emacs] issue affects all Emacs, not merely the newer ones.

It builds on 28 and doesn't on 29. The last successful nixpkgs update was 3 months ago and since then it's been blocking on the E29 build failing. I plan to fix the underlying issues eventually but I've just been putting in the work here and there with no other takers for the most part.

@ckiee mentioned that doom-emacs still doesn't work with emacs29 for some reason. I'd prefer to hold off on dropping emacs28 until next release.

I'd appreciate it if we did

Oops, this PR is automatically closed when I change the target branch from staging to staging-next according to the doc. So I create a new one #272984, which only bumps default Emacs version to 29 and does not remove 28. @vcunat Could you merge that one if it looks good to you?