I find Evil suffers from some of the same problems as viper does: 1) Discoverability. In Emacs C-h b is useful. In vim, :help is wonderful. What does Evil give me that informs me what I can actually type? Referring to vim docs only goes so far. For example, typing d C-h doesn't bring up what I can then type (iw, or whatever). 2) How do I fix my problem? viper and Evil suffer from the same thing: a low-adoption alternative. There will always be a foo-mode out there that doesn't work well. What are the common problems and how do I fix them? I'm an elisp idiot. I get by on copy/paste from others. On Wed, Feb 22, 2012 at 5:24 AM, Vegard Øye <[email protected]> wrote:
On 2012-02-20 21:19 +0100, Leo Alekseyev wrote:
Interesting blog post! It highlights some areas in which the current documentation is rather lacking -- it's been neglected for some time now ...
I've recently been looking to Frank's User Guide for vim-mode as a guide to improving Evil's documentation.[1] What is really needed -- and both your blog post and Frank's guide underline this -- is an overview of the different states and how they relate to Emacs' keymap hierarchy. Rebinding keys and configuring the initial state should also be dealt with in more detail, with instructive examples.
Furthermore, maybe the "Settings" chapter should be moved to the end, since it might be a bit overwhelming up-front. (On the topic of settings, we could perhaps add an `evil-want-sparse-insert-state' customization variable for disabling most of the key bindings of Insert state.)
[1] http://www.emacswiki.org/emacs/VimMode_-_User%27s_Guide
-- Vegard
_______________________________________________ implementations-list mailing list [email protected] https://lists.ourproject.org/cgi-bin/mailman/listinfo/implementations-list