From: Sebastian Urban <mrsebastianurban@gmail.com>
To: 43323@debbugs.gnu.org
Subject: bug#43323: Rename cua-mode to something better?
Date: Sun, 13 Sep 2020 17:49:44 +0200 [thread overview]
Message-ID: <fc8b4c70-eee7-130e-636e-29246f24dac6@gmail.com> (raw)
In-Reply-To: <bbdb25c0-8c39-c20c-d182-07686c7c3a33@gmail.com>
> In my opinion, these menu entry name & manual changes are unnecessary.
So, after reading "Gather a list of confusions beginner tend to have"
thread in emacs-devel, especially (part of) message by Tomas:
Witness: CUA. Most people think these days "CUA" means: "Copy" [1]
is bound to "C-c", "Cut" [2] is bound to "C-x" and "Paste" [3] to
"C-v".
But according to IBM's "Common User Architecture" (aka "CUA" [4]),
it's "C-Insert", "S-Del", and "S-Ins" respectively. But Apple's [5]
infantilised version ("C-x" is the "scissors", etc.) somehow snuck
in.
I guess I was too optimistic about CUA "standard", and proposal to
rename cua-mode to something else, as well as other related changes,
are actually good.
S. U.
next prev parent reply other threads:[~2020-09-13 15:49 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-09-11 0:41 bug#43323: Rename cua-mode to something better? Stefan Kangas
2020-09-11 6:56 ` Eli Zaretskii
2020-09-11 19:19 ` Stefan Kangas
2020-09-11 19:26 ` Eli Zaretskii
2020-09-11 19:41 ` Stefan Kangas
2020-09-12 7:00 ` Eli Zaretskii
2020-09-13 15:58 ` Sebastian Urban
2020-09-14 3:51 ` Richard Stallman
2020-09-11 12:01 ` Sebastian Urban
2020-09-11 17:25 ` Robert Pluim
2020-09-11 19:19 ` Stefan Kangas
2020-09-11 19:41 ` Stefan Kangas
2020-09-11 21:22 ` Sebastian Urban
2020-09-11 21:51 ` Stefan Kangas
2020-09-12 6:18 ` Eli Zaretskii
2020-09-12 18:38 ` Sebastian Urban
2020-09-13 15:49 ` Sebastian Urban [this message]
2020-09-12 5:58 ` Eli Zaretskii
2020-09-13 16:26 ` Stefan Kangas
2020-09-13 16:37 ` Stefan Kangas
2020-09-12 3:19 ` Richard Stallman
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
List information: https://www.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=fc8b4c70-eee7-130e-636e-29246f24dac6@gmail.com \
--to=mrsebastianurban@gmail.com \
--cc=43323@debbugs.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 public inbox
https://git.savannah.gnu.org/cgit/emacs.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).