131–140 of 182 posts
Earlier quoted context omitted.
If you're a firefox user, check this out: https://addons.mozilla.org/en-US/firefox/addon/tridactyl-vim...
Perhaps it's just my wimpy laptop, but last time I tried tridactyl it was pretty slow. Vimium ( https://addons.mozilla.org/en-GB/firefox/addon/vimium-ff/ ) has been a bit better for me, although I think it's quite a bit less configurable than tridactyl.
Earlier quoted context omitted.
If you're a firefox user, check this out: https://addons.mozilla.org/en-US/firefox/addon/tridactyl-vim...
Perhaps it's just my wimpy laptop, but last time I tried tridactyl it was pretty slow. Vimium ( https://addons.mozilla.org/en-GB/firefox/addon/vimium-ff/ ) has been a bit better for me, although I think it's quite a bit less configurable than tridactyl.
Earlier quoted context omitted.
It's funny you mention that. https://www.murilopereira.com/how-to-open-a-file-in-emacs/ The summary is that the author tried to open a remote file and Emacs froze for several seconds. He dived deep into finding out why that was and how to fix it, pointing out how great Emacs's introspection is that one can find solutions to problems like these. And then two thirds of the way into his essay, he has this: > More recent…
Well for what it's worth, here is something about VS Code LSP and embrace-extend-extinguish. https://news.ycombinator.com/item?id=25719338
(Incidentally, I don't even use lsp on Emacs, although I may give it a try).
This article fails to explain -why- one would want to switch to emacs from vim. Org-mode and configuring emacs in a lisp-like are cool, but are not worth re-learning everything for me. I put that time in already by reading "Practical Vim" by Drew Neil and other vim literature online. I'm sure everyone is already aware, but vi is available basically everywhere. This has saved my ass at least twice where I couldn't acc…
I somehow find myself commenting on these threads the most on this site purely to bring up vterm . I think the combination of a well-polished Emacs (like DOOM), evil-mode for vi modal editing everywhere and critically vterm/emacs-libvterm make for a great workflow[1]. Sure there's all the regular Emacs value-adds (Org-mode, Magit, TRAMP etc.) and there's no rush to start learning them, but navigating local/remote cod…
Earlier quoted context omitted.
Vi's sense of composability. For example, 'd' is the delete command, but what does it delete? It deletes across a motion. What is a motion? Could be any movement mode supported by the editor, which ranges from simple cursor motions to motions involving words or blocks to forms of searching to raw line number jumps. So, once you learn a vi command, you can use it with all the motions you already know, and once you lea…
I've used vim for more than 20 years, but lately I'm finding that now that `prettier` and `black` can just reformat code wholesale, I don't have to care as much about the precise tiny edits that vim is so good at. And when I'm not worried about those things, I start to notice that modern IDEs have much smarter syntax checking and whole-project search than I've ever seen in vim, even with plugins. So I think I'm movin…
I’m curious to hear from folks who have switched between the two, and have lasted for more than a year on both. If you’ve learned more than the basics and both became muscle memory, which did you end up sticking to? (Vim user for 23 years, Emacs user of none... but interested because of Lisp)
Vim user for 12 years, Emacs user for 5. I prefer and mainly use Emacs after I finally "got it". My previous attempts at learning Emacs weren't as successful because I was too biased about what a good editor should be like because of my familiarity with vim - mainly I was annoyed about silly things like having to press 4 keypresses for tasks that would take two keypresses in vim. So, if you decide to give Emacs a try…
Recently, I too tried making the switch from vim to Emacs via the Spacemacs route. The effort didn't last long. I found that Spacemacs, without installing any extra "layers" than what comes out of the box, consumes too much RAM. Over 1GB of it. Don't know if this was expected or if it was something specific to just my machine.
Also, if you enjoy the experience provided by emacs + evil, giving a try to the native compilation branch of emacs 28 gives noticeable improvement in terms of speed.
[1] Spacemacs "it's a sophisticated and polished set-up, focused on ergonomics, mnemonics and consistency" VS being focused on speed, https://github.com/hlissner/doom-emacs#introduction
Earlier quoted context omitted.
Well for what it's worth, here is something about VS Code LSP and embrace-extend-extinguish. https://news.ycombinator.com/item?id=25719338
This isn't about LSP but specifically pylance. Let's not confuse the issue. (Incidentally, I don't even use lsp on Emacs, although I may give it a try).
Also the remote extensions are proprietary [1]. This has been discussed on HN before.
Just for fun, here are some of the larger past threads. Others? After over a decade of Vim, I’m hooked on Emacs - https://news.ycombinator.com/item?id=16551796 - March 2018 (161 comments) A pragmatic decision on GNU Emacs versus Vim for programming - https://news.ycombinator.com/item?id=13590944 - Feb 2017 (59 comments) Why I switched from Vim to Emacs - https://news.ycombinator.com/item?id=13130775 - Dec 2016 (101 c…
Emacs vs Vim is like comfort food for software-related online discussions.
In 2001, Slashdot held a poll for Best Flame War. [0] The winner, by quite a margin, was Operating System, but the text editor wars (presently being fought at [1]) weren't listed as an option. Personally I'm also rather fond of the tabs-vs-spaces debate.