Emacs and Vim
martinklepsch.org
Emacs and Vim
1–10 of 277 posts
Re: Emacs and Vim
#2I use Vim on Windows. I tried to learn Emacs but I keep running into roadblocks because of poor Windows compatibility of plugins.
Re: Emacs and Vim
#3I like that he mentioned CtrlP. It's the single plugin that prevents me from switching to Emacs.
There is currently nothing in Emacs (last I played with this was 3 months ago) that is 100% equivalent to CtrlP. There are some close approximations but they're not as good the real deal. I can understand how Emacs guys won't even notice this because they've not worked with something that's better than the best they have, but for Vim guys it sucks.
Re: Emacs and Vim
#4Gah, the tutorial keybindings! They are mad. I've been using emacs for a very long time, and I can't imagine using those to navigate. Emacs has perfectly reasonable default keybindings these days, they just aren't the ones mentioned in the tutorial.
Command: move down one line
What vi uses: j
What the emacs tutorial suggests: C-n
What I use in emacs: the down arrow
Re: Emacs and Vim
#5I like that he mentioned CtrlP. It's the single plugin that prevents me from switching to Emacs. There is currently nothing in Emacs (last I played with this was 3 months ago) that is 100% equivalent to CtrlP. There are some close approximations but they're not as good the real deal. I can understand how Emacs guys won't even notice this because they've not worked with something that's better than the best they have,…
Agree. I'm using projectile[1] for now but that somehow messes things up with caching files so that I actually cannot search my project files. I assume that might be a fault on my side though.
Have you tried projectile? From reading the Readme this was exactly what I was looking for as a Ctrl-P replacement.
Re: Emacs and Vim
#6I use Vim on Windows. I tried to learn Emacs but I keep running into roadblocks because of poor Windows compatibility of plugins.
If you need them, you might consider using the Cygwin(64) version of Emacs. The "w-32" version gives best of both worlds, as it does not need an X server. Be sure to start it with a shortcut so it finds $HOME etc.:
C:\cygwin64\bin\run.exe /usr/bin/bash.exe -l -c emacs-w32.exeRe: Emacs and Vim
#7A relevant comic:
Re: Emacs and Vim
#8Gah, the tutorial keybindings! They are mad. I've been using emacs for a very long time, and I can't imagine using those to navigate. Emacs has perfectly reasonable default keybindings these days, they just aren't the ones mentioned in the tutorial. Command: move down one line What vi uses: j What the emacs tutorial suggests: C-n What I use in emacs: the down arrow
But that means your fingers have leave home row! :(
Re: Emacs and Vim
#9Gah, the tutorial keybindings! They are mad. I've been using emacs for a very long time, and I can't imagine using those to navigate. Emacs has perfectly reasonable default keybindings these days, they just aren't the ones mentioned in the tutorial. Command: move down one line What vi uses: j What the emacs tutorial suggests: C-n What I use in emacs: the down arrow
Usually the strong defenders of emacs tell you that you must use c-n c-p c-b c-f to move because those are better and you will adapt in a short time.
Then the strongest defenders of emacs tell you that you must use whatever you want because the purpose of emacs is that the editor must adapt to you and not the opposite.
Re: Emacs and Vim
#10Until it goes wrong or you have to delve into elisp or you get carpal tunnel...
After 20 years of switching back and forth I decided I wanted an extensible editor not a programming language with an editor built in. That's worked well for me.
I really always just want the simplest thing that will work as I need to rely on it entirely and understand how it works. If I was to use emacs, I'd probably use mg as shipped with OpenBSD.