From: tomas@tuxteam.de
To: xenodasein@tutanota.de
Cc: emacs-devel@gnu.org
Subject: Re: Compatibility
Date: Mon, 7 Feb 2022 12:22:56 +0100 [thread overview]
Message-ID: <YgEBEPxoY7ed9rh3@tuxteam.de> (raw)
In-Reply-To: <MvIiPwV--3-2@tutanota.de>
[-- Attachment #1: Type: text/plain, Size: 1608 bytes --]
On Mon, Feb 07, 2022 at 11:27:49AM +0100, xenodasein@tutanota.de wrote:
> Was: Re: recent change to yanking behavior of the clipboard
> https://lists.gnu.org/archive/html/emacs-devel/2022-02/msg00302.html
> From: tomas
> > ...
> > Psychologically it is extremely... challenging that something "stops
> > working" under you, and you don't even know how that something is
> > called. Perhaps that's part of the reason for the sometimes strong
> > reactions elicited by some changes.
> > ...
>
> 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.
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?
I try as hard as I can to not react to this with resentment. Change is a
fact of life. OTOH, I like to choose what changes I follow along with and
which ones I try to avoid. If sofware supports me with that, I am thankful.
> What am I missing? This is an oft repeated experience and I feel
> unable to understand gist of this matter.
Change. It's a fact of life. That doesn't mean you or me have to like every
change whic comes along :)
(if I have understood you correctly, that is)
Cheers
--
t
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 195 bytes --]
next prev parent reply other threads:[~2022-02-07 11:22 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 ` tomas [this message]
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 ` 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=YgEBEPxoY7ed9rh3@tuxteam.de \
--to=tomas@tuxteam.de \
--cc=emacs-devel@gnu.org \
--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).