Repository navigation
Cover Apple Silicon Macs in the Mac support chapter - #17735
scottjones wants to merge 3 commits into
Conversation
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
[Low impact] No confirmed issue blocks merging this documentation change. SummaryAdds Apple Silicon installation guidance to the Mac support chapter.
Reviews (3) · Last reviewed commit: "Merge branch 'quattro' into docs/mac-sup..." · Reviewed by Greptile |
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
maralcbr
left a comment
There was a problem hiding this comment.
@scottjones re-reviewed at 279c8cb. The only new commit is the merge from quattro, and it leaves the chapter unchanged. The structure is right: Apple Silicon first, Intel under its own heading, and the installer's README for the detail. Two things before merge, neither of them a proven error in the chapter:
- Please check the model list at
manual/44-mac-support.md:5against the catalog a reader gets by default. "Untested" doesn't make "installs" wrong, so I'm not saying line 5 is false. Your draft omacom/omarchy-mac-installer#90 says the edge catalog offers both M3 Airs but shows them as "Untested", and that the seven other M3 Macs keep that note. omacom#604 describes fresh M3 installs on simpledrm.manual/13-toggles-idle-screensaver.md:29mentions "Macs whose GPU isn't supported yet". #90 is about the edge catalog, while line 15 links to the general releases page, so please say whether these Macs are offered on the default channel. If any of that is still current, line 5 should say so. Suggest: "Omarchy installs on M1 and M2 MacBooks, both Air and Pro. It also installs on M3 MacBooks, where the installer marks models that haven't been fully tested as Untested, and where Omarchy may draw on the CPU until the GPU is supported." Add "on the edge channel" if that's where they are. For the MacBook Neo, omacom/omarchy-mac-pkgs#140 mentions it, but only for Touch ID, so please put its catalog entry or a hardware report in the PR body. #90 looks like it covers qualifying the Airs, so this only asks that the page matches the state at merge. testfails at this head. I can't see the log. This PR is unlikely to be the cause: the one test that reads the manual skips stale chapters in its default mode (test/shell.d/i18n-test.sh:42,:227), andi18n-checkruns that same file and passed. The merge does bring in a lot oftest/changes fromquattro. Could you name the failing test, or confirm it also fails onquattro?
Smaller things:
manual/02-getting-started.md:3-5needs an Apple Silicon exception. It says Omarchy is installed from an ISO on a USB stick, while line 21 of the new section says no USB drive is needed. Suggest adding: "On an Apple Silicon Mac, use the installer instead: see Mac support."manual/49-omarchy-on.md:3-5should point here. It still presents Asahi Alarm "with some effort" as the way onto M1/M2. Please add: "For the supported route, see Mac support."- Please add a Verification section (
.github/pull_request_template.md:9-11). Say which installer release and Mac you checked these against: the macOS 15 minimum (:9), thebrewcommand (:18), the shrink and "Loading startup options" flow (:21), and what the README covers (:29). Also say whether the install changes the Mac's startup security. Saying what you couldn't check is fine.
Nits, fine as follow-ups:
- "Installing Omarchy on an Intel Mac" at
:37would read better next to the Apple Silicon section. - The Intel section now opens on the 36% claim at
:33. A lead-in such as "Omarchy runs on Intel Macs, with some known limitations." would help. - I'd give the backup its own bullet at
:11. manual/03-coming-from-mac-or-windows.md:53could mention Apple Silicon too.
For maintainers to decide, not code issues: whether the manual names M3 and the MacBook Neo as supported today and says M4 support "is being worked on" (:5), whether both install routes are endorsed (:15-19), and whether dropping the "built-in support for Intel Macs" sentence is fine in a Mac PR.
For release, not the source merge: :21 and :25 tell people to shrink a working Mac's disk and boot a new OS, and the PR records no walkthrough or hardware result. What evidence the release needs is Marcelo's call.
Reviewed at 279c8cbb1328.
— Marcelo's agent
| ## Apple Silicon Macs | ||
|
|
||
| Please note that installing on an M-series Mac is not directly supported at this time. You can find out more about the state of this in #omarchy-on-other in our [Discord](https://discord.gg/tXFUdasqhY). | ||
| Omarchy installs on M1, M2 and M3 MacBooks, both Air and Pro, and on the MacBook Neo. It goes next to macOS rather than replacing it, so you keep macOS and choose between the two when your Mac starts. Support for M4 and newer Macs is being worked on. |
There was a problem hiding this comment.
Please check this against the catalog a reader gets by default: #90 says M3 Macs show as "Untested" on edge, and the Neo needs a catalog entry or hardware report. Details in the review body.
— Marcelo's agent
|
|
||
| - macOS 15 Sequoia or later | ||
| - Free disk space for Omarchy. The installer suggests a size and lets you change it. | ||
| - A backup of your Mac, power, and an internet connection. The install downloads several gigabytes. |
There was a problem hiding this comment.
nit: I'd give the backup its own bullet.
— Marcelo's agent
|
On the The other points I'll take up with Scott. |
|
I read the chapter diff and the existing review comments at This is waiting for classification to be resolved before verification can proceed. No code or labels were changed, and no tests were run. |
The Mac support chapter still says installing on an M-series Mac isn't supported, which contradicts the 4.5 release and the omarchy.org homepage. This adds an Apple Silicon section at the top: which Macs, what you need, installing with the Omarchy M Installer or
brew install omacom/mac/omarchy, finishing setup in Recovery, and switching between Omarchy and macOS at startup, with the installer's README for the rest. The Intel content moves under its own heading, minus its opening "built-in support" sentence. Translations follow through the usual sync.🤖 Generated with Claude Code