For example, I am no longer in vi-mode if I end up in a help window of some sort. I cannot just Ctrl-W+Ctrl-W my way back to the original window; that suddenly deletes words. But I like working with multiple windows in vim sometimes. This gets frustrating for a vim user.
Also, macros are still not fixed, still using the emacs assumption of what people want for an enhanced vi. We want the easy qq and @q.
Definitely, if you are going to try it out, grab vimpulse. viper-mode is a joke to the developers coming from the vim world. vimpulse makes visual mode highlighting sensible.
That's the logic behind Viper, anyway. I believe a few people are working on a vim emulation layer for Emacs; giving Vim users the ability to have a proper scriptable environment, without having to give up anything they know from Vim. Ask on #emacs.
Where can I see videos of people actually using this text editors? A side by side comparison of interesting/useful features?
I really would like to choose, but the most I managed to find was a guy playing snake on his emacs.
I'm currently using the very basics features of vim, but just because I felt like it and it came with a tutor file.
I think if I could entirely swap out the movement features of Emacs for those of VIM completely, I'd switch tomorrow. That said, Viper and Vimpulse just don't cut it.
Personally, I used emacs and clones (mg and JASSPA MicroEmacs) for a long time- though I never really went very deep into the features. Then, I started a job where I'd be doing some sysadmin work on AIX boxes- nothing but vi and ed installed- so I figured I should sharpen my rusty vi/vim skills. I've found myself using more of the features available in VIM, as well as writing plugins myself. After you get past the initial weirdness (for folks coming from emacs and other modeless editors) I've found it easier. Less of a learning/feature curve, far fewer keystrokes, and almost no "Meta-Shift-Control-Z Ctrl-X abc" acrobatics. UI feels more modular in that I'm stringing together simple commands rather than using a command that does something specific.
Not advocating so much as trying to explain where I came from when I started using vim...
The problem with the "use what you like" approach is that the emacs/vim learning curve are too steep. By the time I am actually using one of them I'll have spent so much that the fear of change starts to strike and I'm stuck with that editor.
For me knowing vim has proven a very productive skill. I often work on random new OS installations like virtual machines and cloud instances, and sometimes in very limited environments like embedded Linux devices. It works there just as well as in my regular Mac/Linux environments.
This is a screenshot of Vim in Emacs in Vim: http://i.imgur.com/fxlm4.jpg
I'd like to know how you're using both vi and emacs. I like both, and used both for a while. Please do tell.
As for using both, I tend to use emacs for the heavy lifting, and vi for quick edits.