I suggest you continue on with your ascent to emacs understanding! Be sure to use something like prelude, i.e. something with 'sane defaults', and checkout this slideshow by emacs enthusiast (and chief designer of ruby) Yukihiro Matsumoto. (http://www.slideshare.net/yukihiro_matz/how-emacs-changed-my...)
It took me 3 weeks to become proficient, and I moved from Sublime Text 2.
As for ergonomics... Emacs bindings feel far more natural and comfortable than any other editor bindings I've ever used, but then I've used Emacs for a long time and am well used to them. I suspect that the same is true for most people: what feels/works best will have more to with what you're used to than any inherent superiority. [And probably no keyboard-oriented editor that's been successful for any length of time will have a truly un-ergonomic design, because it couldn't have succeeded with such.]
Probably the closest thing to what you're describing is the various editor emulation packages, which often remap many basic bindings... Of these, vi/vim emulation is probably the most popular these days, and there are like 4-5 vi/vim emulation packages, of varying degrees of sophistication (and age), although I'm not sure which is the current favorite (maybe "evil"? http://www.emacswiki.org/emacs/Evil ).
I use ST because it just works.
Let me tell you.. Atom will probably never come
close to Emacs programmability and extensibility.
Its by far the most beautiful software
environment. Its a living thing.
In Emacs you're constantly reminded of the love of
generations of hackers in improving it. The
C-core-and-Lisp-scripting pattern was a perfect
match. Emacs has the quality without a name.
But Atom is modern. Emacs is single threaded (IIRC)
and a single evil elisp snippet takes it to its knees.
Those thousands of elisp mdoules (mostly) work together,
without any kind of sandboxing. I think this is also
notable and beautiful. It was achieved by a lot of
hackers who cared a lot.
This is MY little list of people who wrote emacs philosophy or code that I loved, off the top of my head: erik naggum (rip, most people hated him, but he loved
and understood lisp and I want back to old usenet
posts for insights many times
those insights now lost somewhere)
luke gorrie (slime originator iiuc, mind blown w/ his demos.
also erlang guy and hacker at heart
steve yegge (js2, explained emacs qwan in many posts)
sacha chua
TamasPatrovics (anything!)
Eduardo Ochs (eev, built his own little world inside emacs)
David O'Toole (linkd.el, many other intersting packages)
rubikitch (!!! so many useful emacswiki snippets)
alex schroeder (emacswiki master iirc)
Matsushita Akihisa (moccur-edit.el, still miss this in Sublime)
dr qubit
Nikolaj Schumacher (beautiful auto completion packages)
xahlee
magnars sveen
Using emacs feels like being immersed in the rich culture of a past civilization.This was my only contribution to open source and I wish someday I can feel useful in that way again.
Also, I've yet to accept that javascript is taking over (Atom, Lighttable..)
Emacs ftw!
Vim is a very feature-rich editor, which can be distracting while learning the more basic steps. I started with nvi (the vi clone that ships with OpenBSD). Used copys of the 6th edition of O'Reilly's "Learning the vi Editor" (1998) are available practically for free. You don't have to read every single sentence ("remember that you must press ENTER to tell Unix that you are finished issuing your command"), but I found the structure very sensible.
If you don't think distraction is a problem for you, start with Vim and try the vimtutor.
> For example, if you know how to jump to the next occurence of character x (fx), you already know how to delete from cursor to character x (dfx).
Yes but if I have to start typing I have to press some key to switch modes (i?). That is a no-go for me.
That said, there are tricks to make modal editing less annoying. For example, mapping your CAPS LOCK key to ESC makes switching out of insert mode much easier.
Some commands perform actions and then switch modes all at once for you. To extend the grandparent comment's example, you can use the substitute command, s, instead of the delete command, d, to perform the "delete and switch into insert mode" action with sfx (rather than dfx).
Instead, just use it to edit files. After a while, if there is something you are finding would be convenient, search for and or build it.
That said, some obvious points that you will find nice do come by default if you start out with something like prelude. Though, again, just use it to edit files and don't worry about using the keyboard shortcuts that heavily.
If you are highly motivated by the shortcuts, then I would set a pace for learning a few at a time and really get them down first.
For that matter, whether in emacs or atom (or vim/sublime/acme/whatever), it would be rather instructive to see what features are used heavily by folks. Even better if there was a nice listing for what features were discovered, in order and frequency of use.
Is there already a trend/meme for doing something like this? "What I use in my editor?"
The primary reason, at least for non-code text, is that I find it annoying to go back to using stuff like the arrow keys for navigating now that I'm kind of used to the arguably more ergonomic C-f, C-b and friends. So I can echo the sentiment that sticking to the basics of emacs at first can be well worth it.
My advice is to just learn 5-10 basic commands. Movement, copy paste, exit, save and open file. Then see how you like it.
Other than /s, I wanted to say I am also learning emacs after some years of both vim and st2-3 and I really like it. I have still to stick to a cheat sheet to remember common commands but I am on my way to the Stallmanmination