build-emacs-macos VS crafted-emacs

Though I don't love Ventura, running Emacs on MacOS has never really been a problem for me. It's also very easy to build Emacs. You can use this shell script if you like: https://github.com/mclear-tools/build-emacs-macos. I also list there a bunch of other build scripts from other users. Just as easy as homebrew really, with a lot more control (e.g. you can build whatever version of Emacs you like, at least back to 22).

You might find this shell script for building emacs useful. https://github.com/mclear-tools/build-emacs-macos

I build emacs myself from the master branch on an M1 and Monterey and don't see this issue. So it might be something either with your config or with that specific build setup.

Here's the build script that I use. It is pretty dead simple. https://github.com/mclear-tools/build-emacs-macos

Hi all -- I've put a repo on github for building emacs on macos. There are several other such scripts available, but I've tried to make mine as simple to understand (I'm not a programmer) as possible (or as possible for me...). It currently works well for me but YMMV. Of course, I realize that there are a million ways to shave this yak, so I'd be curious if anyone has suggestions for improvement (though I'm also looking to keep things as simple as possible). I hope this might be of some use to people.

Keep an eye on Crafted Emacs which has a v2Beta release branch. It's been evolving. The v2Beta is a rewrite. It aims to provide a minimalist leg up on vanilla Emacs for new Emacs users. It's goal is to take you from first steps to a point where you have learned a great deal and built your configuration. Then you may be comfortable ditching the Crafted Emacs boilerplate configuration entirely. Think of it as a starter kit. Follow SystemCrafters on YouTube (live stream mostly) & Matrix (they are leaving Discord). Despite the live stream being lengthy, there is much to be learned as you bear witness to David figuring things out. Over time, you pickup on those techniques such as looking up a variable state, reviewing functions, evaluating snippets of Elisp in real time, etc. Also recommend, Mastering Emacs as a fantastic ebook with free updates. Once 29.1 ships, no doubt, there will be a free update to the ebook.

I'd recommend you have a look at crafted-emacs. It's an example of how far Emacs can actually go without third-party packages. Then you can add minimal packages (completion and specific tool integrations) to further enhance the experience.

For me it's quite stable except some issues I had with vertico. Anyways, I first started to rewrite my doom config into plain vanilla emacs (with org mode literate configs), and then I discovered crafted which allowed me to remove some code with commonly set sane defaults, e.g. stuff from https://github.com/SystemCrafters/crafted-emacs/blob/master/modules/crafted-defaults.el.

I have been surprised at how many people have so ardently defended only using built-ins and raw package.el and their own janky ensure methods when use-package was available and did it all better. And, it even lets you configure Emacs itself (not just packages), as well as seamlessly letting you try different package management tools like straight.el. Getting it into Emacs itself hopefully makes this a more prevalent way of showing users how to craft their own config.

If you need a staring point for configuring there's some nice light ones like emacs-bedrock and crafted-emacs, and also some fully pre-configured Emacs distributions that you can choose from (though those look harder to configure to one's personal needs to me, but I haven't tried them so wouldn't know).

I'll second https://github.com/SystemCrafters/crafted-emacs

And if you find yourself between the two extremes, perhaps https://github.com/SystemCrafters/crafted-emacs