Emacs 28.1 released

Awesome! Thanks everyone involved for your hard work.

Windows binaries are not there yet, but I guess it won't take long: https://ftp.gnu.org/gnu/emacs/windows/

Great news. Although I'm happily using master branch since the native compilation landed there.

When is 28 going to be official. The website still lists 27 as the latest last time I checked (Sunday)

The only thing I had to change in my ~/.emacs was to remove some key settings in the minibuffer-local-completion-map.

So if you’re using GNU tools on windows, are you actually using GNU+Windows?

GNU/NT

Will this release include native comp by default?

Lmao I just switched to the master branch yesterday

Yes I think this was the release with native-comp, it should start adding .el files to the compilation queue as soon as you start emacs

Awesome

It's official when it hits the FTP site which it already has.

Thank you to the developers!

If you're building emacs you have to ask for native comp when you configure, '--with-native-compilation', it's not on by default.

So there's an announcement today and you expect it to have been on the website yesterday? Time travel sucks.

Right, but I'm asking if this will enable emacs binaries from apt/snap/etc. to use native compilation as well. I know it wasn't the case before this, but I thought 28.1 was the release where it would be enabled.

No I was expecting the announcement for 28 to have been on the website before 28.1 was announced though.

On Emacs the first release is always NN.1, NN.0 is the development release.

It depends on whether the people running those package repositories build with that flag or not.

As long as I've been using emacs I did not know that. Thanks.

Does anyone know if the https://emacsformacosx.com/ version includes native compilation by default? Or do I need to set a flag in `brew` to get it?

Does this one have the Wayland patches merged in?

As far as I can tell, it does not have native-comp enabled. But that's not surprising as it's not yet enabled by default when you build emacs. The [emacsformacosx.com](https://emacsformacosx.com) builds have always strived to be as much vanilla Emacs as possible from what I've understood. My [emacs-builds](https://github.com/jimeh/emacs-builds) project however aims to be a batteries included kind of build. As such native-comp is enabled for all 28.x and later builds, including the 28.1 stable build from April 3rd.

[deleted]

In fact, it may take some time to produce official Emacs 28.1 binaries for Windows. My build scripts are choking. Worse, falling back to manually executing the steps produces (different) errors that I (also) haven't run into before. I plan to open discussions on [devel](https://lists.gnu.org/mailman/listinfo/emacs-devel) to discuss and will share more detail there, in case anyone would like to assist/follow along. Once Emacs 28.1 has been uploaded to the GNU FTP site I'll reply again.

28 has been working as a champ on my end for a while!! [it looks good too! ](https://github.com/Vorlonhomeworld/config/blob/main/2022-04-04-124954_1920x1080_scrot.png)

No, those patches will not be in a stable version until 29 is released. In the meantime, you can get a PGTK-enabled emacs pretty easily via (for example) the Nix package manager with the emacs overlay. The Guix package manager has a similar option available. Both of these package managers should work with most distros.

Congrats! Been using it for a while on Mac and it’s great. Guess it’s time for me to move to 29!

Thank you for your builds!

Thanks to anyone that contributed!

I am waiting for 28.1 is updated in home brew plus so I could install on my MacBook.

Now resolved. I'll make a top-level comment on this post with the deets.

Binaries for Windows are now available from here: https://ftp.gnu.org/gnu/emacs/windows/emacs-28/ Here are the SHA1 Sums: 9709951deeed21292036064447480e0f46106075 \*emacs-28.1-no-deps.zip 3d1fe7ed0012b8a5b8c79c5a391403866e821807 \*emacs-28.1.zip 98cda7a2937431b66cd9a288893a3176db4e69a7 \*emacs-28.1-installer.exe The public key used for signing was: ECE77CF417C76C1ACFCE7C2B5B6135511580F007 You can also find my public key from [Savannah](https://savannah.gnu.org/users/carlc) (press the "Download GPG Key" button).

I installed the Arch version. Does it have native compilation? If so, do I need to add something to my config?

Thank you for posting this! I downloaded and extracted [emacs-28.1.zip](https://emacs-28.1.zip), but when I try to run it with my init file, it got stuck when connecting to [stable.melpa.org](https://stable.melpa.org). I managed to get it working by switching to [melpa.org](https://melpa.org) and copying in gnutls-cli.exe (and associated DLLs) from my emacs-27.2 installation. Did you have any problems like this?

Looks like a [no](https://github.com/archlinux/svntogit-packages/blob/packages/emacs/trunk/PKGBUILD). But if you download that PKGBUILD, you could add "--with-native-compilation" to the end of line 25 and then build it with makepkg. Edit: oh, and also [add 'libgccjit' as a dependency at the end of line 14 and a couple other things](https://bugs.archlinux.org/task/74348?project=1&string=emacs)... From the discussion in the linked bug report, it looks like they are considering a separate "emacs-nativecomp" official package.

I am using Emacs for writing in Persian and its support is great i just want to say thanks to the team for the new release and also supporting Persian

Hi this looks great! Sorry for the dumb question : what differences should I expect compared to emacs-plus?

No worries, first off it’s a pre-compiled binary, so you won’t need to compile Emacs as part of the installation. And secondly the Emacs.app is completely self-contained, so you can safely switch between/rollback to other/older builds by just swapping the Emacs.app bundle. The app is so self-contained that it even works without Homebrew or anything like that installed. The only requirement is Xcode Command Line tools due to native compilation.

YEEESSS!!!! I'll finally have font ligatures!

Thank you!

>Thank you! You're welcome!

Emoji, yes. Font ligatures, no, unless you put in the work to write the support yourself. (I'm still not clear on why there's so much enthusiasm for font ligatures, but different strokes for different folks, I guess)

There's a package called "ligature.el" that only works on Emacs V28+ https://github.com/mickeynp/ligature.el And yes, I love ligatures.

[deleted]

I wasn't aware of that package. Would be nice if they told us what the "bug in core emacs" actually is. And you still don't tell me *why* you love ligatures 🙂

Actually, I did know about that package, I'd just forgotten about it. And yes, it requires emacs-28

I just like the "Fira Code" font

I just downloaded and ran "runemacs.exe" from the archive you mention and I did not face this issue with [stable.melpa.org](https://stable.melpa.org) Emacs did ask for accepting or not a TLS certificate right at startup, before starting to download all the packages in my .emacs. So maybe you were stuck at this point and for some reason the message was not showing up on your Emacs ? You could try to disable some directories in your Windows' PATH and run Emacs again. Maybe there is some .exe in your PATH that is used by the Emacs program instead of the same binary shipped with this Emacs distrib. If there was a missing .exe, I'm pretty sure you would get an error message mentioning it.

The Microsoft IME integration is an absolute godsend.

Are you talking about w32-[g|s]et-ime-open-status? What do they bring?

This [section](https://github.com/jimeh/emacs-builds/blob/main/README.md#homebrew-cask) says native comp isn't supported, but it appears to work. Bummer about lack of M1 support in Github.

Damn, yeah I forgot to update the readme. I’ll sort it out when I’m back on a computer :)

How come imenu and other files are not natively compiled in this release? Shouldn't all lisp files in the distribution be natively compiled already in the binary release?

I think that's a good idea but not yet agreed to by devel team. In the meantime fully ahead-of-time natively complicated (AOT) versions here: https://corwin.bru.st/emacs-28

Thanks. What's the argument against it? Isn't it the most convenient for users who use a precompiled binary release?