Hacker News Reader

Comment by cies | Hacker News Reader

Let me add one Vim tip that recently got me:

http://www.emacswiki.org/emacs/Evil

Seriously, to me it solved all my issues with Vim. Now I have several processes attached to my "Evil", heaps of plugins installed, yet everything blazing fast. And the configuring in elisp started as a little awkward, but now it feels so much more sensible then vim-script (especially knowing that development on Emacs started ding the 70s).

With Evil I can say that --for me-- the Vim/Emacs fight is over:

Emacs now has a great editor...

...and Vim a proper "operating system".

View on HN

I was a long time emacs user, and switched to Vim due to typing pain. Even with Evil, I can't see moving back. Vim + Tmux + YouCompleteMe > Emacs. There's just no comparison. No Emacs shell will ever be as good as zsh, and there's always some latency for some reason when using shells running in emacs. And, there's no youcompleteme.

Evil still lacks q: and q/ for command and search history editing. Really pains me that they haven't implemented this yet. There's also nothing that 100% replaces the CtrlP plugin for Vim on Emacs.

Yeah setting up fuzzy finding on emacs is a huge pain. It's not a hard problem to solve, so maybe if I end up making more use of evil I'll try and write something although elisp is not fun. I currently use helm, ido and projectile and it only kind of works as good as cntrlP or command+T on textmate or sublime text.

same here, also ido+helm+projectile; and not that ctrlP feeling yet.

i think this will be solved though (or is fixable), Vim on the other side does not seem very fixable to me.

I use Evil with emacs prelude now. Has more than enough features I need.

Please vote up the features you think Evil might be lacking, or better yet, contribute to the development effort :)

https://bitbucket.org/lyro/evil/issues?kind=enhancement&sort...

And people complain about UI discoverability in vim, but the fact is if you know how to quit out of vim you will sooner or later bump into the command history; if you experience rogue-like joy in the at this moment you know vim was meant for you.

I don't know if it's by default but Vim also saves search / command history across sessions. So if you quit or accidentally kill the terminal and open Vim again, that history will still be there.

I've been thinking about trying this out for a while now. I just haven't mustered the courage to make the jump. It would be great if there was a tutorial focused specifically on helping vim users who know basically nothing about emacs make the jump.

With that said, is it really worth it if I already use vim along with tmux? This is probably what has kept me from trying out emacs before. Vim isn't an IDE, but with appropriate use of tmux it feels like it can be one.

It's hard to say whether it is worth it. Is there anything you're missing from Vim + Tmux?

The best thing would be to just check it out if you're ever in a playful mood but the chance is pretty big that just playing around with Emacs for an hour will not be enough to convince you to switch.

Feel free to mail me about Emacs so I can help you as Vim user on the way and if you keep notes you can write that "Emacs for Vim users" guide that you asked for.

Reply on news.ycombinator.com