unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Po Lu <luangruo@yahoo.com>
To: tomas@tuxteam.de
Cc: xenodasein@tutanota.de,  emacs-devel@gnu.org
Subject: Re: Compatibility
Date: Mon, 07 Feb 2022 19:57:02 +0800	[thread overview]
Message-ID: <8735kuj3e9.fsf@yahoo.com> (raw)
In-Reply-To: <YgEBEPxoY7ed9rh3@tuxteam.de> (tomas@tuxteam.de's message of "Mon, 7 Feb 2022 12:22:56 +0100")


>> But, why?  Things don't stop working just because, you/an admin makes
>> the choice of replacing the current software with a different, newer
>> one.

Sorry, but that choice was made over two decades ago, so you have to
adapt.  Unless, of course, you stay with Emacs 23 and Qt 2, and not run
any X client written in the past two decades.

> Bu they do. Hardware change. User expectations change, because new users
> enter the scene. Environments change. Not long ago (in geological terms)
> people in my bubble were cutting and pasting with selection/middle mouse
> button, nowadays, with CTRL-C/CTRL_V. "My" bubble has been "invaded" by
> Windows users, so to speak. OTOH, that is a Good Thing, because more
> people get exposed to the idea of free software, ain't it?

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.  For instance, the "Cut" menu item in most
applications would do nothing at all, if it only stored cut text in the
primary selection.

On systems with no primary selection (which Emacs supports), it's even
more meaningless.



  reply	other threads:[~2022-02-07 11:57 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   ` Po Lu [this message]
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         ` Compatibility Eli Zaretskii

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=8735kuj3e9.fsf@yahoo.com \
    --to=luangruo@yahoo.com \
    --cc=emacs-devel@gnu.org \
    --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).