From: Emanuel Berg <moasenwood@zoho.eu>
To: help-gnu-emacs@gnu.org
Subject: Re: Change terminology to better align users’ experience with modern GUIs
Date: Thu, 01 Aug 2019 03:53:34 +0200 [thread overview]
Message-ID: <86blx93b35.fsf@zoho.eu> (raw)
In-Reply-To: 20190723104448.GD27308@tuxteam.de
tomas wrote:
> 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?
Wait, I think I know the answer to this
question! It is "exactly in the way they
reacted", yes?
> 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.
We have heard many versions of this tale,
namely that Emacs is difficult to learn, and
difficult to use, and this scares new users
away; and if those were only more easy to do,
more people would!
I don't know how much truth there is to any of
that, to be honest.
And, unless I'm brained damaged by too much
Emacs, there isn't that much "Emacs jargon",
is it?
> 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.
Well, one can do that for sure, but it comes
down to a policy decision. I can't say I care
if there is a terminology mismatch from the
GUI world to the Emacs ditto, but in general,
obviously it is good to strive at a unified
terminology, while it can be done practically
(perhaps some workaround must be put in place,
so not to break code already written but not
maintained, code which is outside of the core
Emacs binary).
> 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.
Nah, stop it.
> Sorry for that.
It's OK.
--
underground experts united
http://user.it.uu.se/~embe8573
https://dataswamp.org/~incal
next prev parent reply other threads:[~2019-08-01 1:53 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
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 [this message]
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=86blx93b35.fsf@zoho.eu \
--to=moasenwood@zoho.eu \
--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.