Earlier quoted context omitted.
> Vim vs. Emacs is a sideshow at best. Until you need to ssh into a server and edit something.
VS Code supports editing files over ssh. https://code.visualstudio.com/docs/remote/remote-overview
[deleted]
From Vim to Emacs in fourteen days (2015)
81–90 of 182 posts
Re: From Vim to Emacs in fourteen days (2015)
#82Re: From Vim to Emacs in fourteen days (2015)
#83What is this new-fangled Emacs??
WordStar ought to be enough for anybody!
Re: From Vim to Emacs in fourteen days (2015)
#84It probably took me longer than 14 days to learn vim after using emacs for years, it was worth it - mainly and specifically I switched because vim’s modal nature means fewer finger contortions to reach 6 modifier keys simultaneously as required with emacs - that was giving me RSI symptoms. I’ve been happy with vim since and it tends to be more easily available in remote systems. To each their own though - both editors are ok :)
Re: From Vim to Emacs in fourteen days (2015)
#85Earlier quoted context omitted.
It's certainly easier than editing an XMonad config without knowing Haskell.
I don't think that there is an XMonad config file. XMonad is a library and the thing in your home directory is a program that gets compiled into being your window manager, implemented with that library. Emacs and Vim aren't quite like that.
I use both vim and xmonad and have to disagree, as I have a lot of experience configuring both. Config for both is using a file in a programming language specific to each. One being compiled is not a significant difference IMO.
Re: From Vim to Emacs in fourteen days (2015)
#86Earlier quoted context omitted.
Take for example, incremental search. Emacs has it by default. Vi being older didn't have it, but vim has it. It has to be turned on. Then it doesn't work as well as emacs. In emacs you can type to search then ctrl+s to move to next match then continue to type to edit the search string, and so on. This is just one example. Replace has advantages in emacs when it comes to case matching. And it goes on and on.
Incremental search needs to be enabled, yes, but it’s just one line in your .vimrc. What do you mean by “type to search”? Sounds like you’re omitting the “start search” key combo. Your example in Vim: * / to start a forward search * type in the word and hit enter * n/N for next/previous match To modify the search: * q/ opens your search history with the cursor at the last searched string * modify the search string us…
> type in the word and hit enter
That's the problem. When you hit enter you have left incremental search. In emacs you can refine the search string without leaving. Ctrl+s and Ctrl+r goes prev/next and you can simultaneously refine the search string (by typing any other char) without leaving incremental search. Given how important search is (for a programmer) this alone is worth the price of entry. But there are many more things.
Re: From Vim to Emacs in fourteen days (2015)
#87Well I'm long time emacs user who switche to emacs from vi(m) in essentially the time it took to go through the C-h t tutorial.
While today I dont't use Emacs as the day-to-day editor (I use VSCode, for a bunch of not entirely good reasons that mostly have to do with macOS) I think that exposing people new to unix to emacs/zile makes more sense than to vi(m). And then there is the "every mac textfield understands default emacs key bindings" effect...
Re: From Vim to Emacs in fourteen days (2015)
#88I went in the other direction about 5 years ago after 20 years of always installing Emacs on every computer I ever used. Vim has had a much bigger impact on my productivity. Partly because of excellent plugins (VSCode, Visual Studio), partly because, for some reason I bothered to learn Vim shortcuts to degree I never did with Emacs. And I just love that vi and vim is quick and available on my various cloud servers. O…
Fwiw Spacemacs is another good combination of the two, similar to evil mode. https://www.spacemacs.org/
Re: From Vim to Emacs in fourteen days (2015)
#89Earlier 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 can relate. Going from Emacs to evil-mode (not pure vim) has been a bliss. Text and code editing feels almost like playing a game.
Totally agree about it feeling like playing a game. It’s probably because of the combos and just how fast things can be when you move around! I use neovim but I’m sure the experience we have is the same.
Re: From Vim to Emacs in fourteen days (2015)
#90This 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…
> This has been possible for a long time with eshell/shell etc. but vterm really takes the lag out of it IMO. This workflow was certainly my gateway drug to Emacs.
Wait... wait... vterm works with TRAMP? How?
If this lets you navigate remote filesystems as in eshell without the lag on each command that results in... I'm sold.
EDIT: Oh, I found https://github.com/jixiuf/vterm-toggle which seems to open a vterm pane and ssh into the remote host. Which is close enough, I suppose! (Though I would miss being able to just `cp` from a remote path to a local path as if they were both local.)