From: Eli Zaretskii <eliz@gnu.org>
To: Po Lu <luangruo@yahoo.com>
Cc: xenodasein@tutanota.de, tomas@tuxteam.de, emacs-devel@gnu.org
Subject: Re: Compatibility
Date: Mon, 07 Feb 2022 16:18:53 +0200 [thread overview]
Message-ID: <83bkziyd2q.fsf@gnu.org> (raw)
In-Reply-To: <87fsoug526.fsf@yahoo.com> (message from Po Lu on Mon, 07 Feb 2022 21:49:21 +0800)
> From: Po Lu <luangruo@yahoo.com>
> Cc: tomas@tuxteam.de, xenodasein@tutanota.de, emacs-devel@gnu.org
> Date: Mon, 07 Feb 2022 21:49:21 +0800
>
> Eli Zaretskii <eliz@gnu.org> writes:
>
> >> Potential tangent, but I really don't believe that this consensus was
> >> influenced by MS-Windows users. Rather, it was formed by people
> >> generally agreeing that using the primary selection to hold cut text
> >> made little to no sense.
>
> > Because there was no "Cut" back there, AFAIR, there were only
> > selections. Windows didn't have selections (still doesn't), so they
> > impregnated us with the clipboard.
>
> IIRC we had such a cut menu item in Emacs since some time in the early
> Emacs 19 release cycle.
The Emacs parlance for "cut" was "kill"; the "Cut" menu item called
kill-region, which on X would also set the PRIMARY selection.
> CLIPBOARD was also with us since the beginning of selections
Yes, but it was largely unused (except in Emacs on Windows, where we
had no alternative). I'm quite sure that people whose first computer
ran Windows started promoting the clipboard, because they had no idea
what selections were about and how they worked.
prev parent reply other threads:[~2022-02-07 14:18 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-02-07 10:27 Compatibility xenodasein--- via Emacs development discussions.
2022-02-07 11:22 ` Compatibility tomas
2022-02-07 11:57 ` Compatibility Po Lu
2022-02-07 12:54 ` Compatibility tomas
2022-02-07 13:11 ` Compatibility Po Lu
2022-02-07 13:36 ` Compatibility Eli Zaretskii
2022-02-07 13:49 ` Compatibility Po Lu
2022-02-07 14:18 ` Eli Zaretskii [this message]
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=83bkziyd2q.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=emacs-devel@gnu.org \
--cc=luangruo@yahoo.com \
--cc=tomas@tuxteam.de \
--cc=xenodasein@tutanota.de \
/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).