Sandy

I thought of attaching the screenshot of emacs. So the `.emacs` is read correctly, it's the actual async compilation. Here is the warning buffer. Thanks!

@jimeh Thanks for the reply! Launching emacs build from a terminal with `./sources/emacs-mirror-emacs-ed15f39/nextstep/Emacs.app/Contents/MacOS/Emac` launches emacs and the native comp with arm is actually working! So I moved `Emacs.app` from `nextstep`...

I see, @jimeh! Indeed, odd. Uncompressing the built .app in `./builds` and running it crashes with a signature error: ``` Process: Emacs [58096] Path: /Users/USER/*/Emacs.app/Contents/MacOS/Emacs Identifier: org.gnu.Emacs Version: ??? Code...

Interesting, I did hear that M1 arm apps are more strict now. Unfortunately, I don't have an Apple developer account, haven't really worked with signing macOS apps specifically

Yes! It does work and is actually faster than its x86 counterpart. For example, older builds of x86 take about ~4.6 seconds to boot up, while the arm version only...

I think I phrased it oddly, I still have older emacs x86_64 builds (before the code signing commits) from June 2nd, which work great! I'm currently using that x86_64 build...

Actually, M1 can build both! I have two instances of iTerm2, where one is running in native arm mode, the second one is running in Rosetta2's emulation mode. Basically, I...

Here are two of my emacs versions I have right now! Yes, I always built Intel versions on my M1

I'll try the emacs builds later and will write an update on how it goes here. So from the picture above, you can see I have my x86_64 version build...

> Oh, that's actually very interesting. And your x86 Emacs build have `Application (Intel)` as kind if you Get Info on the app? I've had a few friends try x86...