After keeping my Emacs configuration somewhat static for a few years, I have made some bigger changes recently. I changed which packages I am using for core functionality such as completions and search. This post highlights some of them and the reasons behind choosing them. I should note that I have only used some of them for a week, so I am still at the very beginning of my learning journey. I guess learning Emacs is a never-ending rabbit hole!
This poem was made by ChatGPT.
I have been using Emacs the normal way for many years and I am really happy with it. By normal, I mean starting Emacs as a regular process and not using the daemon with emacsclient. This approach has been good enough because usually I start Emacs once when I start working and then just keep it running throughout the day. The startup time is not too bad, maybe around a second or two, when it happens only once per day. With the faster startup speed usually described as the main benefit of the daemon process, I had not seen the need for it in my workflow. But now I changed my system to run not one, but two, daemon processes of Emacs, and I am really glad I made the change.
I have been using Emacs as my text editor for a few years now. One of the best features about emacs is that you can customize everything. This is because of the underlying lisp interpreter that allows you to define custom functions and then bind them to keys. This is in contrast to a "normal" text editor which allows you to change keybindings, but only to pre-defined built-in functions which perform the text manipulation.