emacs-plus: current state
Not everyone knows, but emacs-plus is almost an April Fool’s joke that was late for 1 day. Its initial release was on 2nd April 2016 and the only feature it had compared to the official Emacs formula back in the day was Spacemacs icon (installed by default). Homebrew maintainers didn’t want to increase the complexity of the Emacs formula, so I’ve put that burden on myself, created a tap with one additional icon and after several years info command for
emacs-plus prints a wall of options.
I am very happy to see so many users of this feature-inclusive (and sometimes experimental) formula. I am grateful to all of you. I would’ve abandoned this project a year ago if it would not you! And I think it’s fair to (in)formally share the current state of the project and shed some light on my plans.
During the last year (or maybe even more),
emacs-plus overgrown with issues. Here is my top list.
xwidgetsbuild was breaking time to time and only thanks to users (mostly Ag Ibragimov) I would acknowledge it.
- While I state that
HEADbuilds are not supported, I still want this option to work. First of all, for Emacs users to easily get the latest features. And secondly, for Emacs maintainers to get feedback from the users.
- Patches are located outside of the project and their destiny is unclear.
- It’s hard to contribute a new patch or a patch fix inside the
emacs-plusrepository, because you have to mess with the URLs and branch names.
- Travis builds are very slow. The default build takes 7 minutes, from sources - 13 minutes, build HEAD was impossible. I’d like to test much more build options and their combination.
- Too many options are given to the users, which kind of contradicts my initial idea.
When it comes to build failures, all of them can be divided into two categories - patch application failure or upstream issue.
Visibility and stability
In order to address the named issues, I’ve performed the following actions.
I moved from Travis to GitHub Workflows, which gave such a decent boost in compiling time. It also enabled me to add the
xwidgets options to the build matrix. I would love to add
x11 as well, but I didn’t figure out how to setup XQuartz on build machines. I haven’t really measured the build time, but here are some examples that I fetched from the build history. Also I’ve heard that Travis improved their machines so more calculating power is given to the users now.
|6m 30s||3m 14s|
||11m 16s||5m 18s|
This gives me better visibility on the build breakages (both when patch application fails or it’s because of the upstream issue).
All of the used patches were moved to the
emacs-plus repository, so they are always with formula. And I added support for running builds on CI with patches from PR.
And in order to better maintain the patches I’ve created emacs-plus-basis repository, which is basically a fork of Emacs repository with patches applied on top. Everyday CI fetches the latest updates from the upstream and applies the patches on top. And if it fails, I get a notification. So it gives me visibility of patch application failures. And it gives me environment to fix named patches.
While all these steps should improve stability of the
emacs-plus, I am aware that build breakages are impossible to avoid (upstream changes very fast). What I am achieving here is better visibility and tools to address breakages more quickly.
Build options zoo
What was not covered yet is the amount of build options. The initial idea behind
emacs-plus is that users should not pass many custom options to
install command. If you remember, back then everyone recommended to install Emacs from brew using the following command:
$ brew install emacs --with-cocoa --with-gnutls --with-rsvg --with-imagemagick
All of these options where recommended to most of the users. So I decided to turn them on by default.
$ brew install emacs-plus
In my ideal world, the only options users should pass is the icon choice and experimental or controversial stuff.
I still don’t have a solution, but I am willing to decrease amount of available options. For example, I think that no one actually installs without cocoa and without x11. So the choice must be between these two options. GnuTLS? Well, why would anyone want to install Emacs without it?
libxml2? Does it hurt if installed with it? I want
emacs-plus be as simple as possible, while still providing things that are not available from the official Emacs formula.
Unfortunately, I don’t have anonymous statistics about options usage. So I still don’t have any decision in this field. Will keep you posted :)
This is something people are waiting for. I understand why, but I don’t have time to invest into this project. At least now. If someone wants to step in - I would be super glad and grateful!
That being said, all contributions are welcome! Let’s keep in touch ;)