Getting Started with Emacs & Doom in 2021 (on Apple Silicon M1) · Emacs Doomcasts 27

[@RahulKumar-mh4bk]

Adding the font: - Homebrew: ❯ brew tap homebrew/cask-fonts ❯ brew install --cask font-iosevka-aile font-iosevka-ss04 Checking the fonts: - In macos `Launchpad` -> fonts book -> installed inside {Computer(for all users) or User} - Check the fonts available inside the `User` and put them inside fonts ~/.Doom/config.el - Then press SPC h r f to refresh fonts - Then restart emacs using SPC q r

[@kabirkang2154]

When I do this, Emacs opens up as a blank white screen. Not sure how to debug this.

[@JoeHassick]

@@kabirkang2154 Have you tried reverting back to the original font or trying a different one? Try also setting the `doom-variable-pitch-font` to Iosevka SS04. Your blank screen should be related to a missing font. You may be missing Iosevka, SF Pro Text, or both.

[@esgasi07]

Yo man, i love how your terminal looks, do you have a video about how to make the same look?

[@jeetadityachatterjee6995]

It's not recommended to use SPC h r r. But to use doom sync on the commandline as that regenerates some files that Emacs will reload on startup. If you are having a problem I recommend doom sync and restarting Emacs

[@zaisteprogramming]

Thanks for clarifying!

[@MattGalles]

SPC h r r didn't reload the fonts for me like it did in the video. I'm new to emacs so I'm not sure what I did wrong.

[@MrOlegrom]

@@MattGalles the command that he used was SPC h r f

[@Gjermund-Sivertsen]

For the fonts: Where do you put them after install? I get error when trying to apply, doing exactly what you did. Thanks for the video!

[@LatestLeak]

i followed exactly too and i'm getting font error issue as well

[@npradeeptha]

I am curious about performance on the M1. Could you talk a bit about how M1 is performing vs x86 mac? When you have fully set it up of course :)

[@servallou2514]

M1 is wonderful, M2 I think it's made in heaven

[@naavidmorshed5516]

I know im two years too late but I recently started learning emacs and it runs smooth as butter. For the first 3-4 times I opened as "emacsclient -c", it cause some hiccups during keyboard navigation. That all went away now and I have no complaints, but do not expect it to be as fast as neovim. It's not even a competition.

[@npradeeptha]

@@naavidmorshed5516 I agree 100% on the speed difference. I used Doom emacs for 2 years and loved it. No issues on the M1 mac (max) and I thought it ran smooth until I switched to neovim a few weeks ago. The speed difference is day and night. Neovim has come a long way since a couple of years ago and I don't really feel like i'm missing anything from emacs. I thought I wouldn't be able to live without Magit but lazygit is just fine for my needs. Magit still feels more polished but lazygit gets the job done. I also feel the plugin ecosystem for nvim is superior to that of emacs. They get more frequent updates and it's super fast to pull in all the updates at startup. I like the speed and I am not sure I can go back.

[@naavidmorshed5516]

@@npradeeptha I'm still not 100% sure on sticking to doom/emacs for programming but I'll definitely learn it for org mode, magit, and latex. I've been using intellij idea for 3 years and I might stick to it for vim mode, better refactoring and debugging or completely switch to neovim.

[@johncrwarner]

I installed Doom Emacs on a Raspberry Pi and noticed the "markdown" flag when I ran Doom Doctor and I hunted for markdown compilers that worked on the Raspberry Pi ARM 64 bit architecture and had no joy... until I found marked which is a node.js app which is "built for speed" and was trivial to install and took away the warning issued My x86-64 computers (my actual workhorses) didn't have this problem - but they already had pandoc installed.

[@boopfer387]

Thank you!

[@senwhich]

Thank you for useful video, helpful especially where you copy directory to applications, here I was stuck before. Would like to ask, I have also uncommented vterm however after typing space o t it says: is undefined, so not even what appears in your case: Vterm needs 'term-module' to work. Complie it now? (y or n). How can I get the vterm inside the emacs? I like the way you explain as I am beginner.

[@kabirkang2154]

There's an issue with these instructions related to the font. I get a blank white screen opening Emacs after doing the font instructions.

[@Billilv]

you can check the existing fonts with iterm2's setting dialog or any app that have a setting for you to choose font.

[@hberto]

One thing can be nice to see is your usage of Tmux with Doom Emacs. What theme are you using at terminal?

[@bosmanka]

Works perfectly on my Mac mini M1. Thanks. BTW, what terminal are you using?

[@ZeushadesChannel]

My vterm-module installation does not work saying the architecture is x86_64 not arm64e. I followed your guide exactly, do you have a clue as to why this might be the case (I am M1) thanks

[@JoeHassick]

I have an M1 and ran into issues opening vterm. My error was "Cannot open load file". I had to install cmake and libvterm and then things began working as expected. brew install cmake libvterm

[@Jaan2103]

What terminal are u using? which theme is this?

[@The33xion]

Im super new to everything. When I refresh the font nothing happens, but when I do "Command x and command e" to execute the change then refresh the font it works. It looks like for you just changing the text in the config makes it change when you "space h r f". Why does that not work for me?

[@潘奕辉]

Very useful tutorial!

[@Johnvardas]

Is this running natively or some kind of rosetta stuff?

[@kaiser2568]

When I run bin/doom doctor it tells me „EMacs was not built with native compilation support“ I’m very new to Unix and all of this so I’m not really sure what to do, do I need to restart and download with native support or what?

[@phanta5m]

the emacs-plus should have option like --with-native-comp for brew install command. but in my machine it make emacs really slow ( mb pro m1)

[@celestialadministration]

Want to do doom emacs

[@OpenMicDropNight]

😄