Emacs

Arguably the most successful platform whose code can be easily modified at runtime. Emacs presents this through the metaphor of a text editor, though the Emacs platform has been about more than that since pretty much its inception. Emacs as a platform hosts email[1] readers, Usenet[2] clients, web and Gopher[3] browsers, games, terminal emulators, sftp clients, chat clients, and even a window manager. With org-mode[4], most of these (including the email clients) can be linked together with agendas, task lists, and personal notes to form an integrated tracking system. org-roam[5] extends this yet further.

1: /email/
2: /usenet/
3: /gopher/
4: /org-mode/
5: /org-roam/

As a text editor, it is remarkably proficient, with specialist features for dozens of programming languages and support for both Emacs and vim-style keybindings.

I believe it is a mistake to regard Emacs as simply a text editor.

I wrote a blog series on Emacs[6] that has a lot of detail. My Emacs #1[7] may be particularly helpful.

6: https://changelog.complete.org/archives/tag/emacs-s9y
7: https://changelog.complete.org/archives/9861-emacs-1-ditching-a-bunch-of-stuff-and-moving-to-emacs-and-org-mode
Homepage: https://www.gnu.org/software/emacs/

The Emacs Wiki[8] is also great.

8: https://www.emacswiki.org/

--------------------------------------------------------------------------------

Links to this note

9: /org-roam/
According to its website, org-roam is "a plain-text personal knowledge management system". It is based on the popular Zettelkasten knowledge management system, or the Roam Research website. But because it layers atop org-mode[10] and therefore Emacs[11], it has a lot of power that the others lack; for instance, integration with email and agendas.
10: /org-mode/
11: /emacs/
12: /org-mode/
org-mode is a toolkit for you to organize things. It is part of Emacs[13].
13: /emacs/
14: /old-and-small-technology/
Old technology is any tech that's, well... old.

More on www.complete.org

Homepage
Interesting Topics
How This Site is Built
About John Goerzen
Web version of this site

(c) 2022-2024 John Goerzen