4 ms·
Looked through the repo readme, as I had free time. First advice, enable emacs as a daemon, if you haven't already. And replace most of emacs shortcuts you use,
by aviranzerioniac 5y ago
Looked through the repo readme, as I had free time. First advice, enable emacs as a daemon, if you haven't already. And replace most of emacs shortcuts you use, as in keyboard shortcuts or EDITOR to emacsclient, helps with startup.
-> Or it stops activating modes that I hooked to specific buffers.
Maybe because some buffers try to activate two or more modes by default. Do try looking through that. One major mode and many minor at the same time is what works.
1. Resources, primarily, documentation for emacs, org-mode. And few blogs which extensively do emacs articles. Google search does work good for those.
2. It is not like you'd turn into an expert after debugging just some issues. It will take time, a lot of it probably. And you will feel like you did waste some time. Take what you want from it.
3. I used doom for some time, before making my own config. If you feel configuring is time consuming, you can choose one (Doom/Space) and forget about it. With the types of devices we normally have, a few seconds is nothing. but preparing your own config gives you a new look into emacs, and helps in future trouble-shooting as you know what is in the configs.
- shivekkhurana 5y agoEmacs daemon was never on my radar, I'll look into it. Thank you.