Emacs Mini Manual

Dev tools

editor documentation

SHOW HN2014

130points
41comments
#206of 2,272 in 2014
Top 10%of 2014 by points

How HN took it

MixedNo clear lean

11 positive, 3 neutral or asking, 1 mixed, 3 critical, out of 18 comments about the project. Thread score +0.47.

Docs: 6 for, 2 againstExecution: 1 for, 1 against

The thread, comment by comment

Each row is a top-level comment and its replies, in HN's order. Select a cell to open that comment on HN.

positive neutral or mixed critical about another commenter or something else the maker

What HN said

What people liked

  • Good introduction for newcomers and a useful reference for existing users.

    From 2 comments
    • This looks like an excellent resource for those new to emacs, and a good reference for those already using it. All written in org-mode as well. Thank you
      MarcScott on HN
    • Definitely good for someone already using it. At least in my case.
      jzzskijj on HN
  • Well-made, impressive resource.

    From 3 comments
    • This is really impressive, I'm starting to try Racket coding with Emacs + Geiser Mode. And I really need some sort of Guides to rely on once in a while. The following words also…
      pimgeek on HN
    • I don't use Emacs, but this is great. Nice work.
      yoanizer on HN
    • Well done.
      nodivbyzero on HN

Objections

  • Prose has many grammatical errors.

    From 2 comments
    • Nice work. It would be nice if you can find a native English speaker, or at least someone with stronger English skills, to edit (in the literary sense) your prose. You manage to…
      neonscribe on HN
    • Almost every sentence needs work. What you need is a writer who is fluent in English to spend a few hours going over it.
      neonscribe on HN
  • Would not install or run on Windows.

    From 1 comment
    • I've seen this page before but couldn't get anything to work in Windows.
      Yuioup on HN
  • Teaching only stock Emacs is poor advice for programmers.

    From 1 comment
    • > If you want advance[d] techniques, the primary resource should be Emacs Lisp Manual, Emacs docstrings, and learn[ing] code written by package maintainers. (I'm also learning…
      klibertp on HN

Requests

  • Advanced Emacs technique material is needed.

    From 1 comment
    • http://tuhdo.github.io/emacs-tutor.html#text-7-29 - the excersise: ``` C-f to the beginning of each character group and add whitespace. ``` No, don't! Use C-s or even better…
      klibertp on HN
  • Re-record animations showing key presses.

    From 1 comment
    • Also, I have a suggestion (completely unrelated to my ramblings): could you maybe re-record the animations with some program showing what keys you press enabled? It would make…
      klibertp on HN
  • A similar guide for Vim.

    From 1 comment
    • Wow, this is great but I'm a vim user. I'd really love to have something in this format for vim. Maybe something like that already exists but I just don't know about it yet?
      wyclif on HN

Questions

  • How to save window layouts between Emacs sessions.

    From 1 comment
    • I learned how to record the window layout with register, but I also want it to be recorded for next time. but I would like to record this for next time I use emacs. How to do this?
      emlearn5 on HN

Alternatives named

  • Projectile for project navigation and grep.

    From 1 comment
    • You should use Projectile: https://github.com/bbatsov/projectile . Projectile allows you to Grep a project under VCS easily. And use Helm with it like this:…
      tuhdo on HN
  • Workgroups2 for saving window configurations.

    From 1 comment
    • You need extension package. Workgroup2 is great for this: https://github.com/pashinin/workgroups2 With workgroups2, windows configurations can be stored in a workgroup, and you…
      tuhdo on HN
  • Prelude starter kit.

    From 1 comment
    • > If you want advance[d] techniques, the primary resource should be Emacs Lisp Manual, Emacs docstrings, and learn[ing] code written by package maintainers. (I'm also learning…
      klibertp on HN

Category, keywords, summaries and labels on this page were made by AI (Thread Reader v2) and not checked by hand. Each point links to the comments it came from.

Add a badge to your READMEShown on HackerShow
[![Shown on HackerShow](https://hackershow.org/badge.svg)](https://hackershow.org/show/8118233)