unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Po Lu <luangruo@yahoo.com>
To: Stefan Monnier <monnier@iro.umontreal.ca>
Cc: xenodasein--- via "Emacs development discussions."
	<emacs-devel@gnu.org>,
	 xenodasein@tutanota.de
Subject: Re: recent change to yanking behavior of the clipboard
Date: Mon, 07 Feb 2022 21:15:07 +0800	[thread overview]
Message-ID: <878rumhl7o.fsf@yahoo.com> (raw)
In-Reply-To: <jwvmtj23kgl.fsf-monnier+emacs@gnu.org> (Stefan Monnier's message of "Mon, 07 Feb 2022 08:04:19 -0500")

Stefan Monnier <monnier@iro.umontreal.ca> writes:

>> I see no point in sticking to behaviour obsoleted by the operating
>> system, such as storing cut text in the primary selection.  On X, every
>> client has to cooperate with every other client in order to have working
>> cut and paste, and a single client deviating from that is sufficient to
>> bring down the entire deck-of-cards.

> Now I'm lost.  What you say here seems to claim that the change under
> discussion brings Emacs in line with the official/standard protocol.
> Yet that change is very specific to the `CLIPBOARD` whereas I'd expect
> such an official protocol to behave the same for all types of selections.

No, this is something else unrelated to the original change: I'm trying
to coinvince people not to use `select-enable-primary', at least
lightly, and those prior changes you referred to changed the default
value of `select-enable-primary'.  Further down another thread someone
said that was common advice on the internet, which is shocking, since
that amounts to teaching people to break their systems.

> Elsewhere you said that the motivation was one of optimization
> of performance.  Yet Noah's original message points out a change in
> actual behavior rather than mere performance.
>
> I'm having difficulty reconciling those somewhat contradictory facts.
>
> Could someone walk me through step-by-step what happens in one or two cases,
> (e.g. Noah's case, or the "normal" case) explaining what Emacs does and
> why, how the patch affects the outcome and what the ideal behavior would
> be according to the standard protocol?

We don't know what happens in Noah case yet.  He hasn't replied to my
questions.

Thanks.



  reply	other threads:[~2022-02-07 13:15 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.
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 [this message]
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=878rumhl7o.fsf@yahoo.com \
    --to=luangruo@yahoo.com \
    --cc=emacs-devel@gnu.org \
    --cc=monnier@iro.umontreal.ca \
    --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).