That’s how the meme goes though. Anytime someone suggests, says something positive about one of vim or emacs, the response should be that they should use the other. 😄
micro is nice, I’ve been using it more for the past few months
And for me, there was no productivity penalty when switching from VSCode, since I didn’t have to learn all new keybinds (still lacks a bit of multicursor, tho)
Vim is a super fit girl who wants you to go rock climbing with her, and you’re kinda scared of her.
Emacs is a big plenty-of-everything roundaway girl who wants to wrap you up in a cuddle and learn to make your favorite food and binge watch nerdy documentaries with you.
I think the story goes that if you stick around too long, ignoring the red flags and warnings from your friends, one day you wake up in a bathtub full of ice and she’s on her way to the highest bidder with your kidneys in a cooler.
It’s very easy to pick up. Out of the box, it’s just Evil, Ivy/Vertico, Org-mode, and several programming modes. The spacebar is likewise employed for many actions, but I don’t use most of them myself: just have about a dozen that I invoke regularly. The enabled modules (readymade configuration) and installed packages are specified in config files, and doom sync handles installing them.
It has some emacslisp helper functions/macros to add mappings, add hooks on modes, etc. — these are more convenient than those of raw Emacs.
I’m not sure why the author switched Doom to Vertico in the upcoming version 3, when Ivy was working fine. I’ve made some configuration tailored to Ivy, so enabled it back via the config file.
You really should use vim though.
No (I already somewhat learned Emacs, I ain’t gonna learn something new)
That’s how the meme goes though. Anytime someone suggests, says something positive about one of vim or emacs, the response should be that they should use the other. 😄
It’s an almost 40-year-old flame war.
Me:
Go, nano!
I even tried micro.
me want nano. nano edit important file pulsar can’t. dolphin angry if me use like administrator.
micro is nice, I’ve been using it more for the past few months
And for me, there was no productivity penalty when switching from VSCode, since I didn’t have to learn all new keybinds (still lacks a bit of multicursor, tho)
That wikipedia article is pure comedy gold
Glad to lighten up the day!
Vim is a super fit girl who wants you to go rock climbing with her, and you’re kinda scared of her.
Emacs is a big plenty-of-everything roundaway girl who wants to wrap you up in a cuddle and learn to make your favorite food and binge watch nerdy documentaries with you.
Please do VS Code. 😁
I think the story goes that if you stick around too long, ignoring the red flags and warnings from your friends, one day you wake up in a bathtub full of ice and she’s on her way to the highest bidder with your kidneys in a cooler.
🙌
nvim
ftfy
The vim key bindings are a lot better.
🫴 https://github.com/emacs-evil/evil
Yeah, I daily drive spacemacs. 🙂
https://www.spacemacs.org/
I found Doom to be a good middle-ground between raw Emacs+Evil and a complete overhaul of Spacemacs.
I’ve thought about Doom, but I haven’t gotten around to trying it out. Finding the time to sit down and learn it hasn’t been a high priority.
It’s very easy to pick up. Out of the box, it’s just Evil, Ivy/Vertico, Org-mode, and several programming modes. The spacebar is likewise employed for many actions, but I don’t use most of them myself: just have about a dozen that I invoke regularly. The enabled modules (readymade configuration) and installed packages are specified in config files, and
doom synchandles installing them.It has some emacslisp helper functions/macros to add mappings, add hooks on modes, etc. — these are more convenient than those of raw Emacs.
I’m not sure why the author switched Doom to Vertico in the upcoming version 3, when Ivy was working fine. I’ve made some configuration tailored to Ivy, so enabled it back via the config file.