From: xenodasein--- via "Emacs development discussions." <emacs-devel@gnu.org>
To: luangruo@yahoo.com
Cc: emacs-devel@gnu.org
Subject: Re: recent change to yanking behavior of the clipboard
Date: Sun, 6 Feb 2022 12:55:00 +0100 (CET) [thread overview]
Message-ID: <MvDsmQ7--3-2@tutanota.de> (raw)
In-Reply-To: <87fsownrml.fsf@yahoo.com>
Thing is, this time you seem to think that you are "fixing" things,
and someone else thinks it breaks 30 year old behavior. See some
pattern here? I'd focus on that instead of the "see this see that"
smarty-pants-ery.
Feb 6, 2022, 14:47 by luangruo@yahoo.com:
> xenodasein@tutanota.de writes:
>
>> So? Emacs is not and hopefully will never be a dedicated X11 "app."
>>
>
> On the contrary, the system we want to support best is the GNU system,
> of which X11 is an important component. Certainly more important than
> Wayland, which after 10 years continues to be immature and annoy users
> (see bug#53793 for a recent example.)
>
next prev parent reply other threads:[~2022-02-06 11:55 UTC|newest]
Thread overview: 55+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-02-06 11:07 recent change to yanking behavior of the clipboard xenodasein--- via Emacs development discussions.
2022-02-06 11:21 ` Po Lu
2022-02-06 11:37 ` xenodasein--- via Emacs development discussions.
2022-02-06 11:47 ` Po Lu
2022-02-06 11:55 ` xenodasein--- via Emacs development discussions. [this message]
2022-02-06 12:01 ` Po Lu
2022-02-06 12:06 ` xenodasein--- via Emacs development discussions.
2022-02-06 12:08 ` Eli Zaretskii
2022-02-06 12:15 ` xenodasein--- via Emacs development discussions.
2022-02-06 12:30 ` Eli Zaretskii
2022-02-06 12:15 ` tomas
2022-02-06 12:20 ` xenodasein--- via Emacs development discussions.
2022-02-06 15:20 ` Stefan Monnier
2022-02-07 1:18 ` Po Lu
2022-02-07 13:04 ` Stefan Monnier
2022-02-07 13:15 ` Po Lu
2022-02-07 19:47 ` James Cloos
2022-02-07 19:53 ` tomas
2022-02-06 15:17 ` Stefan Monnier
-- strict thread matches above, loose matches on Subject: below --
2022-02-06 3:39 Noah Friedman
2022-02-06 7:37 ` Po Lu
2022-02-06 9:20 ` Eli Zaretskii
2022-02-06 9:34 ` Po Lu
2022-02-06 10:18 ` Po Lu
2022-02-06 16:09 ` Óscar Fuentes
2022-02-07 1:11 ` Po Lu
2022-02-07 2:05 ` Óscar Fuentes
2022-02-07 2:59 ` Po Lu
2022-02-07 5:04 ` Óscar Fuentes
2022-02-07 5:17 ` Yuri Khan
2022-02-07 5:23 ` Óscar Fuentes
2022-02-07 5:31 ` Po Lu
2022-02-06 22:39 ` Lars Ingebrigtsen
2022-02-07 1:12 ` Po Lu
2022-02-07 2:53 ` Lars Ingebrigtsen
2022-02-07 3:11 ` Po Lu
2022-02-07 3:41 ` Lars Ingebrigtsen
2022-02-07 3:48 ` Po Lu
2022-02-07 4:05 ` Lars Ingebrigtsen
2022-02-07 4:44 ` Po Lu
2022-02-07 4:57 ` Corwin Brust
2022-02-07 5:29 ` Po Lu
2022-02-07 5:47 ` Corwin Brust
2022-02-07 5:52 ` tomas
2022-02-07 6:43 ` Po Lu
2022-02-07 6:57 ` tomas
2022-02-07 13:17 ` Eli Zaretskii
2022-02-07 13:18 ` Po Lu
2022-02-07 12:49 ` Eli Zaretskii
2022-02-07 12:56 ` Po Lu
2022-02-07 13:14 ` Stefan Monnier
2022-02-07 13:17 ` Po Lu
2022-02-07 1:11 ` Tim Cross
2022-02-07 2:31 ` Michael Welsh Duggan
2022-02-06 9:17 ` 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=MvDsmQ7--3-2@tutanota.de \
--to=emacs-devel@gnu.org \
--cc=luangruo@yahoo.com \
--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).