11–20 of 47 posts
The install section is out of date, at least for macos homebrew. The emacs-plus package on homebrew ( https://github.com/d12frosted/homebrew-emacs-plus ) is the best for macos.
My learning path was 1) use vim/nvim for a couple years 2) use Doom Emacs. I was shocked at how intuitive Doom is for me. Of course not everyone would agree but it’s worth checking out
We used emacs in college and that was the last time I used any text editor serverside besides vi. Am I missing out?
My learning path was 1) use vim/nvim for a couple years 2) use Doom Emacs. I was shocked at how intuitive Doom is for me. Of course not everyone would agree but it’s worth checking out
My learning path was 1) use vim/nvim for a couple years 2) use Doom Emacs. I was shocked at how intuitive Doom is for me. Of course not everyone would agree but it’s worth checking out
More recently I've been reading the Org manual (1), which like Spacemacs opened my eyes to Org mode's capabilities: literate programming and code blocks that modify the source document captured my interest, along with table and spreadsheet capabilities.
I still use nvim all the time in the terminal; vi knowledge is essential, as it's the best editor you can be sure to have on a UNIX-like system. Case in point: Today I used vi in kterm on my jailbroken Kindle Touch to edit usbnet's SSHD config (2) and I can't imagine a more efficient editor (3) for an eInk device.
P.S. My favorite thing about Emacs is the help system. Being able to look up a function or what a key does with a few keypresses is fantastic!
1: https://orgmode.org/org.pdf
2: Now I can use `scp` or SFTP from my laptop and or iPhone to add books to my Kindle while it's connected to my iPhone hotspot
In vi (which apparently is vim by default I was told?) I know open, save, quit, go to line, go to begin/end of line, find, insert, delete line. We used emacs in college and that was the last time I used any text editor serverside besides vi. Am I missing out?
Emacs is a great extensible platform for writing textual applications that happens to come with a mediocre text editor. If you like automating things or enjoy having development environments that fit you like a glove, you'll want to learn Emacs - it'll pay off in a few years. (this describes me)
But not everyone fits that description, and that's totally fine. I know many software engineers who have been working for decades in vanilla vim, and they're still incredibly productive. VSCode, too, comes with sane out of the box defaults and a large extension ecosystem.
There's probably an analogy to be made here between flexible languages (Lisp, Haskell, C++ kind-of) and inflexible languages (Python, Java) - some people really want to develop DSLs to perfectly express their problem, but others are ok with a slightly awkward mismatch due to a rigid language, and are still incredibly productive and happy.
(however, aside from practical use, I find the design of Emacs to be quite beautiful and inspiring, and encourage you to take a look at it anyway when you have some time)
This tutorial is painfully out of date, and I would argue a very bad way to learn emacs today. As an example, don't learn to use ETags unless you are going to specifically be working with a C project where other developers use them. You would be better served these days learning LSP and treesitter, which is now built-in. I would also strongly suggest using Doom Emacs, and working your way backward to a minimalist con…
> You would be better served these days using LSP and treesitter
Could you elaborate? How do I transition from etags to treesitter? Suppose I'm working on a dynamic C or C++ project where I might need to regenerate the tags daily.
This article has an interesting perspective. But, beyond Emacs built-in documentation, my favorite content to learn Emacs is the book Mastering Emacs and the System Crafters' YouTube Channel.
My learning path was 1) use vim/nvim for a couple years 2) use Doom Emacs. I was shocked at how intuitive Doom is for me. Of course not everyone would agree but it’s worth checking out
