Hacker Newsnew | past | comments | ask | show | jobs | submitlogin

It's also useful for teaching new features. If you are mindful of the existence of achievements, you might check the list once in a while and see something like "Fast Copy - Use Ctrl-C to copy something instead of clicking on the button!"


The best thing about achievements are that they teach you new ways to play a game (IMO). When I play a game with well-designed achievements, I'm constantly learning: "Oh, I can approach enemies this way." Or they make me try a new weapon type: "Oh, this weapon is effective in this situation, now I will update my default play-style." I would love to have such achievements for Emacs, because I feel like I don't use it to its potential, but I also don't have a good sense of directions to explore.


I would recommend: When you want to customise the behaviour of some command, don't google for the answer. Instead do `C-h f` or `C-h k` to read the built-in documentation for that function or key. From the help screen, click the link to view the function's source code -- if you don't see that link install the "emacs-el" package (using your system's package manager). See what variables that function uses. Do `C-h v` to read the documentation for each variable.

If you like this approach, I've written a guide (http://david.rothlis.net/emacs/customize_c.html) which, at 3,000 words, is half the length of the Emacs manual table of contents.


If you're already comfortable, the next best thing to do is start reading the Emacs manual from start to finish.

You'll soon run across things you don't take advantage of (it was registers and org-mode for me).


Just play a round of `M-x keywiz` each morning.




Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: