From: 조성빈 <pcr910303@icloud.com>
To: help-gnu-emacs@gnu.org
Subject: Change terminology to better align users’ experience with modern GUIs
Date: Tue, 23 Jul 2019 15:46:31 +0900 [thread overview]
Message-ID: <58E90D68-5CE4-425F-BB5F-07533665ADC0@icloud.com> (raw)
Is there any intent or interest in updating the terminology of Emacs documentation/function names to better align users’ experience with modern GUIs?
For example, `window' and `buffer' in emacs is more meaningful when explained as `pane' or `document'.
Especially the term `window' is a frequent source of confusion to Emacs newcomers which confuse them to `frame'.
IMO in my ideal world, there should be no division between `window' and `buffer', the difference should be abstracted away so that users don’t have to know the `window' notion at all.
However that currently isn’t the case, there are multiple occurrences (and a dedicated chapter) in the Emacs manual about `window' and `buffer'.
Changing the `window' term to `pane' or something else seems like a low-hanging fruit for people who would like to try using Emacs; I’m interested/curious on other people’s opinions about this.
(Sorry about my bad English skills :-()
next reply other threads:[~2019-07-23 6:46 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-07-23 6:46 조성빈 [this message]
2019-07-23 9:37 ` Change terminology to better align users’ experience with modern GUIs 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
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=58E90D68-5CE4-425F-BB5F-07533665ADC0@icloud.com \
--to=pcr910303@icloud.com \
--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.