[implementations-list] How important is a Vimpulse user manual? How to make one? Copy from Vim docs?

Jason Spiro jasonspiro3 at gmail.com
Wed Feb 10 09:52:13 CET 2010

On Tue, Dec 29, 2009 at 2:49 PM, Vegard Øye <vegard_oye at hotmail.com> wrote:

> This is often referred to as the "Emacs pinky" problem, but I don't
> think it's Emacs specific, having done careful comparisons with other
> mature editors like TextMate, jEdit and SlickEdit. Guess what I found?
> They all suffer from the same Ctrl-Shift-Alt clutter. The simple fact
> is that if the editor is non-modal, keyboard-oriented and rich in
> features, overloading of the modified keys is just inevitable.
> The paradoxical truth is that it is feature-heavy Emacs, often touted
> as the arch-enemy of modal editor Vim in an epic "editor war", which
> would benefit the most from a modal interface.

Wow.  I like your analysis a lot.

> At the same time, I think stand-alone Viper requires too much
> knowledge too early: for instance, there's no h/j/k/l navigation in
> the help buffers, as Viper disables itself in a number of cases to
> avoid overriding special keymaps. I suggest Vimpulse slightly augment
> these keymaps with basic vi navigation (but without overwriting
> anything) to avoid infinite recursion: "vi keys don't work in Help,
> use Emacs keys instead. To learn Emacs keys, use the Help system."

I think people can just use the arrow keys and Enter in Info mode.  :)

More information about the implementations-list mailing list