@returntrip@mastodon.technology the main question for me is if the "old" will be a problem for me. Emacs in Flatpak was pretty quirky when I tried it, and even if it would work great it would be inconvenient as my workflows now depend on Emacs launching containers a lot (e.g. to run LSP servers and tests).

Fedora Workstation is an option of course, but feels silly for _one_ program (even if it is Emacs).

@bkhl I missed the original post, so I'm guessing at the original issue. But what about (a) just building Emacs from source? or (b) using Nix's/Guix's Emacs on top of whatever distro you're using?


@emacsomancer @returntrip@mastodon.technology yup, if that's the only application that's an issue with using a longer term release distro I might just compile my own Emacs.

@bkhl I compile my own anyway since I'm using Emacs 28.0.5. It's not a major burden.


@emacsomancer @returntrip@mastodon.technology yeah, wouldn't think so. I guess I will do it the minute I find something lacking in Emacs 26, which is what RHEL is currently on. It's not _that_ old, so maybe I won't even notice the difference ...

@bkhl depends mainly on what packages you use probably. there could be something targeting 27. but 26 is only a couple of years old.


@emacsomancer @returntrip@mastodon.technology the main thing is the JSON parsing performance improvements, since I use LSP a lot. I guess I'll find out soon if it's fast enough anyway.

Sign in to participate in the conversation
Mastodon @ SDF

"I appreciate SDF but it's a general-purpose server and the name doesn't make it obvious that it's about art." - Eugen Rochko