From: Robert Pluim <rpluim@gmail.com>
To: excalamus--- via "Emacs development discussions." <emacs-devel@gnu.org>
Cc: excalamus@tutanota.com, Eduardo Ochs <eduardoochs@gmail.com>
Subject: Re: GNU Emacs raison d'etre - 1981-ish version
Date: Fri, 15 May 2020 10:55:34 +0200 [thread overview]
Message-ID: <m2blmpziex.fsf@gmail.com> (raw)
In-Reply-To: <M7K470g--3-2@tutanota.com> (excalamus's message of "Thu, 14 May 2020 23:26:05 +0200 (CEST)")
>>>>> On Thu, 14 May 2020 23:26:05 +0200 (CEST), excalamus--- via "Emacs development discussions." <emacs-devel@gnu.org> said:
Emacs> Emacs presents a challenge to the user. The challenge can be solved
Emacs> through programming, but the user is unable to do this. To help,
Emacs> Emacs provides ready made components, functions bound to keys, which
Emacs> complete the task when chained together. The user realizes at some
Emacs> point that 1) these actions are functions and 2) they have the ability
Emacs> to write them. Emacs provides the structure required for the user to
Emacs> learn through source code (higher skill set) and C-h f (assistance).
This is a good explanation of why Emacs is the only editing system
that doesnʼt drive me up the wall: I can mold it as I see fit.
Emacs> I believe that other editors could occupy this space but do not.
Emacs> Other editors are either word processors or IDEs. Emacs is a hybrid;
Emacs> there are authors who use Emacs solely for writing and the are
Emacs> developers who use it solely for programming. Emacs feels different
Emacs> because it shortens the distance between question and answer. Other
Emacs> editors require searching externally (does MS Word even still have F1
Emacs> help?). Emacs can be searched inside and out.
Which is one of Emacs' great strengths, but I fear the current
generation are missing out on it: I see lots of problem reports saying
"website so and so says this, but my Emacs behaves differently", where
the solution is to consult the documentation inside emacs. It appears
people have become conditioned to doing a web search for manuals,
which often donʼt correspond to their installed version (as a
corollary, people almost never specify platform and/or version
either in such reports).
Robert
next prev parent reply other threads:[~2020-05-15 8:55 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-05-14 6:24 GNU Emacs raison d'etre - 1981-ish version Eduardo Ochs
2020-05-14 16:45 ` Drew Adams
2020-05-14 21:26 ` excalamus--- via Emacs development discussions.
2020-05-15 8:55 ` Robert Pluim [this message]
2020-05-15 10:18 ` Eli Zaretskii
2020-05-16 4:19 ` Richard Stallman
2020-05-18 15:27 ` Robert Pluim
2020-05-19 3:54 ` Richard Stallman
2020-05-19 4:39 ` Stefan Kangas
2020-05-19 4:51 ` andres.ramirez
2020-05-21 3:42 ` Versions of Emacs Manuals on web Richard Stallman
2020-05-21 5:22 ` andrés ramírez
2020-05-21 8:02 ` Joost Kremers
2020-05-21 15:20 ` Drew Adams
2020-05-21 15:47 ` Stefan Kangas
2020-05-21 16:13 ` Drew Adams
2020-05-21 3:42 ` Richard Stallman
2020-05-21 13:19 ` Eli Zaretskii
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=m2blmpziex.fsf@gmail.com \
--to=rpluim@gmail.com \
--cc=eduardoochs@gmail.com \
--cc=emacs-devel@gnu.org \
--cc=excalamus@tutanota.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.