Install Emacs via the omarchy-emacs AUR package#6329
Conversation
Point the Emacs entry in the install-editor menu at a dedicated omarchy-install-editor-emacs script, matching the pattern already used for Helix, VSCode, and Zed. The script installs the omarchy-emacs AUR package and runs its installer, which pulls in emacs-wayland, applies the theme/font integration, and enables the user emacs.service. This is the AUR-packaged approach dhh suggested on basecamp#4807 (superseding the in-tree integration proposed there), now that the package exists and is maintained on the AUR. End-user behavior is unchanged except that a freshly installed Emacs now tracks the active Omarchy theme and font out of the box. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
There was a problem hiding this comment.
Pull request overview
This PR updates Omarchy’s editor installation menu so the Emacs option installs the dedicated omarchy-emacs AUR package (and runs its installer) via a new omarchy-install-editor-emacs helper script, aligning the Emacs flow with the existing “setup-based editor” pattern used by Helix/VSCode/Zed.
Changes:
- Switch the Emacs menu action to run
omarchy-install-editor-emacsin the floating terminal presentation wrapper. - Add
bin/omarchy-install-editor-emacsto installomarchy-emacsfrom AUR and invokeomarchy-install-emacs.
Tip
If you aren't ready for review, convert to a draft PR.
Click "Convert to draft" or run gh pr ready --undo.
Click "Ready for review" or run gh pr ready to reengage.
Reviewed changes
Copilot reviewed 1 out of 2 changed files in this pull request and generated no comments.
| File | Description |
|---|---|
| default/omarchy/omarchy-menu.jsonc | Points the Emacs install entry at the new dedicated installer script via the standard floating-terminal presentation wrapper. |
| bin/omarchy-install-editor-emacs | New installer entrypoint that installs the omarchy-emacs AUR package and runs its setup installer. |
💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.
screenrecording-2026-07-20_20-23-40-compressed.mp4 |
|
Lovely. Let's get omarchy-emacs added to omarchy-pkgs too. So we don't have to rely on AUR. You can open a PR here: https://github.com/omacom-io/omarchy-pkgs. Then we can install using the regular non-AUR installer. |
|
Glad you like it. I've had so much fun creating it and using Omarchy (I almost decided to try to learn vim instead). Thank you! |
* Add omarchy-emacs Emacs integration for Omarchy with automatic theme and font syncing, synced from the AUR (source: aur). Requested by @dhh in basecamp/omarchy#6329 so it can be installed from the Omarchy repo via the regular installer rather than relying on the AUR at install time. - AUR: https://aur.archlinux.org/packages/omarchy-emacs - Source: https://github.com/scottjones/omarchy-emacs Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com> * Drop install scriptlet from omarchy-emacs (sync 1.8.9) Per review: user-side setup is invoked by the Omarchy installer, so the pacman post_install/post_upgrade scriptlet is redundant. Re-synced from AUR at 1.8.9, which removes it. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com> --------- Co-authored-by: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
|
I thought there were some setup gymnastics you had to do as well? The ones we yanked from the package? The installer here should get you all the way to a running emacs. Preferably even open it after install, like we do with the other editors. |
Summary
omarchy-install-editor-emacsscript, matching the pattern already used for Helix, VSCode, and Zed.omarchy-emacsAUR package and runs its installer, which pulls inemacs-wayland, applies the theme/font integration, and enables the useremacs.service.Context
This is the AUR-packaged follow-up to #4807, where @dhh suggested packaging the Emacs integration as an AUR package (like
omarchy-nvim) rather than shipping it in-tree — thank you for that steer. The package now exists and is maintained:It supersedes #5329, which made the same change against
devbefore the quattro menu refactor landed. I'll close that one in favor of this.Behavior
Before:
omarchy-install-app Emacs emacs-wayland && systemctl --user enable --now emacs.service— installs a bare Emacs with no theming.After: installs an Emacs that automatically tracks the active Omarchy theme and font, with the daemon enabled. The AUR package encapsulates setup, so the menu line stays a one-liner consistent with the other setup-based editors (Helix/Zed/VSCode).
Test plan
omarchy-install-editor-emacsruns cleanly — installs the package, runs setup, enables and startsemacs.serviceomarchytheme applied, tracking the current theme at~/.local/state/omarchy/current/omarchy-menu.jsoncstill parses; the entry launches viaomarchy-launch-floating-terminal-with-presentationlike the other setup-based editors