For pure text surgery, I'm still significantly faster in Vim. But the fact that Emacs is so explorable/discoverable is just so fun!
For pure text surgery, I'm still significantly faster in Vim. But the fact that Emacs is so explorable/discoverable is just so fun!
Have you tried viper mode or one of the equivalents? I'm curious how it compares to vi. One of the things that I (as a long time Emacs user) have considered is to switch to using viper mode, even though I only know vi enough to edit a config file on a remote machine that lacks emacs. But I'm curious how it compares to the real thing, and if it gets in the way of ancillary emacs stuff (I can't live without stuff like "C-x v =" and "M-/").
The difference between Vim and the original vi is pretty huge. Just as an Emacs user might be stymied by the missing Lisp support in uemacs or zile, a habitual Vim user leans on stuff like text objects and visual selections, which were never even a twinkle in Bill Joy's eye.
(emacs is actually a bit unwieldy by comparison - * was one of the things I missed when I left vim. I was also used to using this same functionality in Visual Studio and Scite (it's Ctrl+F3), so it was well embedded into my workflow.)
set incsearch
in your ~/.vimrc[1]: http://blog.sanctum.geek.nz/vi-mode-in-bash/ [2]: http://zshwiki.org/home/zle/emacsandvikeys