From: <tomas@tuxteam.de>
To: help-gnu-emacs@gnu.org
Subject: Re: Change terminology to better align users’ experience with modern GUIs
Date: Tue, 23 Jul 2019 12:44:48 +0200 [thread overview]
Message-ID: <20190723104448.GD27308@tuxteam.de> (raw)
In-Reply-To: <58E90D68-5CE4-425F-BB5F-07533665ADC0@icloud.com>
[-- Attachment #1: Type: text/plain, Size: 2169 bytes --]
On Tue, Jul 23, 2019 at 03:46:31PM +0900, 조성빈 wrote:
> Is there any intent or interest in updating the terminology
> of Emacs documentation/function names to better align users’
> experience with modern GUIs?
Patience, young padovan :-)
Emacs has a working and dedicated community. If you just enter
through the door and say "Hello, everybody: how about we change
all names of things, like, now?"... how do you think people
will react?
Nevertheless you do have a strong point: the Emacs jargon, evolved
over a long time (few software packages in productive usage can look
back on thirty years of history) definitely poses a barrier to entry
for newcomers. Nobody wants that, thus constructive proposals to
change that are, I'm sure, welcome.
Change in Emacs is gradual (but still can be radical [1]), this
is a thing many of its users appreciate highly (I do, for one:
Emacs is one of my main tools, and I can afford to live on the
bleeding edge and compile for me the "newest Emacs" every week
or so. I wouldn't dare to do that with most other software out
there)!
So a good strategy, if you're really hot & willing to change
things would be to grab the documentation, and perhaps write
a companion to the documentation "Glossary" (let's call it
"Anti-Glossary" which translates "current" terms into the
Emacs terminology. So someone searching for "window", "pane",
"cursor", etc. has a chance to hit on the relevant documentation.
A next step might be to cross-index those "current" terms
with the "traditional" ones.
Whether you manage to convince enough people to really change
the language is anyone's guess, but you can start some steps
into that general direction.
P.S: Sorry if this mail comes across as somewhat... condescending.
This is not my intention at all! If that's the case, it is more
due to my inability to put things shortly and clearly.
Sorry for that.
Cheers
[1] I'd highly recommend reading
https://www.iro.umontreal.ca/~monnier/hopl-4-emacs-lisp.pdf
It's only about the Lisp part of Emacs but gives an impression
on how much has happened over time.
-- tomás
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 198 bytes --]
next prev parent reply other threads:[~2019-07-23 10:44 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-07-23 6:46 Change terminology to better align users’ experience with modern GUIs 조성빈
2019-07-23 9:37 ` Jean Louis
2019-07-23 10:13 ` 조성빈
2019-07-23 17:03 ` Gerhard Wolfstieg
2019-07-23 19:17 ` tomas
2019-07-23 22:12 ` Stefan Monnier
2019-07-23 10:44 ` tomas [this message]
2019-07-23 14:43 ` Eli Zaretskii
2019-07-23 16:15 ` tomas
2019-07-23 16:48 ` Eli Zaretskii
2019-08-03 17:37 ` Emanuel Berg
2019-08-01 1:53 ` Emanuel Berg
2019-07-23 11:38 ` Noam Postavsky
2019-07-23 13:00 ` Stefan Monnier
2019-07-23 13:11 ` MBR
2019-07-23 13:40 ` tomas
2019-07-23 13:46 ` Noam Postavsky
2019-07-23 13:59 ` tomas
2019-07-23 14:38 ` Stefan Monnier
2019-08-03 17:12 ` Emanuel Berg
2019-08-01 1:55 ` Emanuel Berg
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=20190723104448.GD27308@tuxteam.de \
--to=tomas@tuxteam.de \
--cc=help-gnu-emacs@gnu.org \
/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.