[bheadmaster]

> Nobody really reads 18 chapters of documentation before making keyboard mappings. I make keyboard mappings and I read 0 chapters of the documentation. 0. Zero. How? Just like you do anything else in software these days? Looking it up, jumping directly to the documentation I needed to learn how to do key maps.

Yes, and that's the approach I used multiple times, the same approach that helped me learn Vim. The learning curve is much steeper, and Vimtutor is much easier to comprehend than the C-t h tutorial.

That's what I tried to say in the first comment, and people attacked me by saying Emacs has awesome documentation. Now you're attacking me, saying that documentation doesn't matter and nobody reads it anyway...

[mapreduce]

> that documentation doesn't matter and nobody reads it anyway

Did I say that? I don't think so. I said that it is possible to create key mappings without reading 18 chapters of documentation. How? By looking up what we need.

But Emacs users do read the documentation but not necessarily in a linear manner where they must start from Chapter 1 and go all the way to Chapter 18 before they are able to do something. Some people might it read like that. But most people including myself read the parts that matter to us.

[bheadmaster]

> Did I say that? I don't think so. I said that it is possible to create key mappings without reading 18 chapters of documentation. How? By looking up what we need.

And I said that approach didn't work for me. Great that it worked for you, but I found that looking stuff up for Vim was much easier than looking up stuff for Emacs. Which is what I basically said in the first comment and explained several times in this comment thread.