build-emacs-for-macos VS doom-emacs

I built emacs from source, native comp, a few months ago and recently heard about pgtk. Is this worth it (for more smoothness, better user experience) on MacOS? I saw this thread: https://github.com/jimeh/build-emacs-for-macos/issues/45 where it was mentioned that you have to turn off the MacOS specific flag, so I’m not sure if it’s more harm than good, and what benefit it may serve. Anyone have experience optimizing their emacs on MacOS as much as possible? I basically run native comp vanilla emacs with only about 100 lines in my init file, which I byte compile (I’m not sure if the init file byte compilation helps? It seems like even though packages get compiled down natively, going into the native code folder (alongside byte compilations) , init.el doesn’t have an option for it).

Details about the helper is in the readme here, and source for the helper is here.

I've been stuck on a build from February 23rd, I think, because all other builds since then have had some instability or funny quirks. Just built this today from source (thank you build-emacs-for-macos) and it's been solid so far!

Hi fellows, I am using this repo to build emacs on aarch64 mac. During the building, there are a lot of warning messages like:

I recognized your avatar. You're the one behind https://github.com/jimeh/build-emacs-for-macos . Nice project, I am using it to produce the macOS binary.

update: tried this build script and seems good

https://github.com/jimeh/build-emacs-for-macos

I've been using this: https://github.com/jimeh/build-emacs-for-macos

I use https://github.com/jimeh/build-emacs-for-macos which makes the custom build really easy.

Alternatively if you prefer to compile Emacs on your machine, there’s emacs-plus and my own build-emacs-for-macos which both have options to enable native compilation for 28.x and later builds.

I would recommend building from source like this for MacOS nowadays: https://github.com/jimeh/build-emacs-for-macos

$ rm -rf ~/.config/emacs # Remove the existing directory if necessary git clone --depth 1 https://github.com/hlissner/doom-emacs ~/.config/emacs ~/.config/emacs/bin/doom install

Sounds like what you want is emacs, but preconfigured. In that case, have you tried Doom Emacs, Spacemacs or any of the myriad of others like those?

darren@pop-os:~$ git clone --depth 1 https://github.com/hlissner/doom-emacs ~/.emacs.d Cloning into '/home/darren/.emacs.d'... remote: Enumerating objects: 1156, done. remote: Counting objects: 100% (1156/1156), done. remote: Compressing objects: 100% (1042/1042), done. remote: Total 1156 (delta 85), reused 650 (delta 71), pack-reused 0 Receiving objects: 100% (1156/1156), 1.13 MiB | 7.29 MiB/s, done. Resolving deltas: 100% (85/85), done.

I used to do something like -{ nixosConfig, config, lib, pkgs, ... }: -let - xdgConfig = config.xdg.configHome; -in { - home.activation = { - foo = lib.hm.dag.entryAfter [ "writeBoundary" ] '' - doomdir="${xdgConfig}/doom"; - # $VERBOSE_ARG - if [ -d "$doomdir" ]; then - $DRY_RUN_CMD git -C "$doomdir" pull http master || true - else - # git clone and change url - http="https://git." - $DRY_RUN_CMD git clone "$http" "$doomdir" - # the new url needs ssh keys setup - git -C "$doomdir" remote add http "$http" - git -C "$doomdir" remote set-url origin "gitea@git." - fi - emacsdir="${xdgConfig}/emacs" - if [ -d "$emacsdir" ]; then - if [ -d "$emacsdir/.local" ]; then - $DRY_RUN_CMD $emacsdir/bin/doom sync - fi - else - $DRY_RUN_CMD git clone --depth 1 https://github.com/hlissner/doom-emacs "$emacsdir" - fi - ''; - }; -}

`;; Needed to add javascript-eslint to the the next-checker after lsp so that it would actually load, as that wasn’t happening by deafult ;; also needed to runit after the lsp-afer-initalize-hook because otherwise ‘lsp wasn’t a valid checker (add-hook ‘lsp-after-initialize-hook (lambda () (flycheck-add-next-checker ‘lsp ‘javascript-eslint))) ;; https://github.com/hlissner/doom-emacs/issues/1530 ;; Potential alternative to the above ;; (after! (:and lsp-mode flycheck) ;; (flycheck-add-next-checker ‘lsp ‘javascript-eslint))

The performance lag of Spacemacs was addressed by Doom Emacs ( https://github.com/hlissner/doom-emacs ). Have you tried Doom Emacs by any chance. After syncing everything, the performance is stellar in my opinion.

but I just realized, you're probably better off using doom emacs. The defaults are sane, customizations are almost always optional and the community's really active/helpful. (Disclaimer: I'm a doom emacs user with ~2k lines of config)

While Doom is more opinionated, it's not too difficult make Emacs your own, most of the choices are optimized anyway. Currently the head of Spacemacs devs is not active on the project anymore. Also I don't think it's hard to upstream code to Doom, as long as the code is thoroughly written, take a similar example on both sides: the introduction of a completion engine as layer/module (same packages are installed): - https://github.com/syl20bnr/spacemacs/pull/14901: 23 comments, 7 participants - https://github.com/hlissner/doom-emacs/pull/4664: 576 comments, 20 participants

Also Doom emacs has one. https://github.com/hlissner/doom-emacs https://github.com/hlissner/doom-emacs/tree/master/modules/lang/common-lisp

Nowadays, I use https://github.com/hlissner/doom-emacs with WSL2 but only for org-mode. For code, I have either Sublime Text or VS Code.