Our great sponsors
-
-
-
WorkOS
The modern identity platform for B2B SaaS. The APIs are flexible and easy-to-use, supporting authentication, user identity, and complex enterprise features like SSO and SCIM provisioning.
-
-
ripgrep
ripgrep recursively searches directories for a regex pattern while respecting your gitignore
-
InfluxDB
Power Real-Time Data Analytics at Scale. Get real-time insights from all types of time series data with InfluxDB. Ingest, query, and analyze billions of data points in real-time with unbounded cardinality.
-
github-orgmode-tests
This is a test project where you can explore how github interprets Org-mode files
A few days (and a lot of reading documentation and running rg and fd over Doom Emacs's source code) later, I have to say I'm impressed! I was expecting Emacs to be excellent, no surprises there; what I didn't expect was how passionate and active the community is. It's honestly inspiring seeing how much time and effort is being put into the various community projects, across the board. The only packages I knew I wanted to try were Magit and use-package, so I had a lot of fun exploring other packages. I was worried I'd quickly get overwhelmed, but the process was made so much easier with the help of: Emacs's self-documentation, Doom's source code and FAQ, the documentation provided by the individual packages and helpful answers and posts online.
Hello, everyone! As it says in the title, this is my first time trying Emacs (although, technically, my second time installing it). I had been using Neovim exclusively prior to that and absolutely loving it (I still do), but I always knew I wanted to try out Emacs at some point. A few days ago I heard about native-comp coming to Emacs 28, and given that the Nix emacs-overlay provided emacsGcc, now seemed like the perfect time to do so!
Hello, everyone! As it says in the title, this is my first time trying Emacs (although, technically, my second time installing it). I had been using Neovim exclusively prior to that and absolutely loving it (I still do), but I always knew I wanted to try out Emacs at some point. A few days ago I heard about native-comp coming to Emacs 28, and given that the Nix emacs-overlay provided emacsGcc, now seemed like the perfect time to do so!
A few days (and a lot of reading documentation and running rg and fd over Doom Emacs's source code) later, I have to say I'm impressed! I was expecting Emacs to be excellent, no surprises there; what I didn't expect was how passionate and active the community is. It's honestly inspiring seeing how much time and effort is being put into the various community projects, across the board. The only packages I knew I wanted to try were Magit and use-package, so I had a lot of fun exploring other packages. I was worried I'd quickly get overwhelmed, but the process was made so much easier with the help of: Emacs's self-documentation, Doom's source code and FAQ, the documentation provided by the individual packages and helpful answers and posts online.
A few days (and a lot of reading documentation and running rg and fd over Doom Emacs's source code) later, I have to say I'm impressed! I was expecting Emacs to be excellent, no surprises there; what I didn't expect was how passionate and active the community is. It's honestly inspiring seeing how much time and effort is being put into the various community projects, across the board. The only packages I knew I wanted to try were Magit and use-package, so I had a lot of fun exploring other packages. I was worried I'd quickly get overwhelmed, but the process was made so much easier with the help of: Emacs's self-documentation, Doom's source code and FAQ, the documentation provided by the individual packages and helpful answers and posts online.
A few days (and a lot of reading documentation and running rg and fd over Doom Emacs's source code) later, I have to say I'm impressed! I was expecting Emacs to be excellent, no surprises there; what I didn't expect was how passionate and active the community is. It's honestly inspiring seeing how much time and effort is being put into the various community projects, across the board. The only packages I knew I wanted to try were Magit and use-package, so I had a lot of fun exploring other packages. I was worried I'd quickly get overwhelmed, but the process was made so much easier with the help of: Emacs's self-documentation, Doom's source code and FAQ, the documentation provided by the individual packages and helpful answers and posts online.
A few days (and a lot of reading documentation and running rg and fd over Doom Emacs's source code) later, I have to say I'm impressed! I was expecting Emacs to be excellent, no surprises there; what I didn't expect was how passionate and active the community is. It's honestly inspiring seeing how much time and effort is being put into the various community projects, across the board. The only packages I knew I wanted to try were Magit and use-package, so I had a lot of fun exploring other packages. I was worried I'd quickly get overwhelmed, but the process was made so much easier with the help of: Emacs's self-documentation, Doom's source code and FAQ, the documentation provided by the individual packages and helpful answers and posts online.
Speaking of Doom, I can't remember what I was looking for at the time, but I came across Doom's exit prompt, doom-quit. Admittedly, I'm not cool enough to understand all the references, but I loved it so much that I just had to find a way to include it in my configuration.
You should also take a look at org-mode.
I also faced the magit GIT_DIR thing. Details of my setup are here
Related posts
- Potencializando Sua Experiência no Linux: Conheça as Ferramentas em Rust para um Desenvolvimento Eficiente
- Telescope grep features dont work on windows, how can i make them work?
- Don't try this at home
- Who knew about the rip grep ? You can easily search for the text contents in your files and it's super fast.
- Installing Doom Emacs on Windows