From: Stefan Monnier via "Bug reports for GNU Emacs, the Swiss army knife of text editors" <bug-gnu-emacs@gnu.org>
To: Lars Ingebrigtsen <larsi@gnus.org>
Cc: Eli Zaretskii <eliz@gnu.org>,
27442@debbugs.gnu.org, Constantine Kharlamov <Hi-Angel@yandex.ru>
Subject: bug#27442: Un-obsolete x-clipboard-yank, or provide analogous functional
Date: Mon, 05 Jul 2021 11:59:32 -0400 [thread overview]
Message-ID: <jwv7di4ycwz.fsf-monnier+emacs@gnu.org> (raw)
In-Reply-To: <87eeccwzjx.fsf@gnus.org> (Lars Ingebrigtsen's message of "Mon, 05 Jul 2021 17:28:02 +0200")
> *ponder* Well, I guess it's a vague kind of DWIM thing going on...
> Since we don't have timestamps on our own kills, and
> `select-enable-clipboard' defaults to t, we want to let a clipboard
> selection "win" if we haven't yanked it before? But... it seems to me
> like this is already handled by other logic when putting things on the
> kill ring in the first place.
That pretty much matches my understanding, yes.
> That is, if you "emacs -Q", put something on the clipboard from a
> different programme, and when `M-w' something in Emacs, then `C-y' will
> insert the latter.
Yes, IIUC this is the easy case. I think the harder case is when we
`M-w` first and then put something on the clipboard with another
application, then do `C-y`.
> I've tested various things here now, and I'm unable to come up with a
> scenario where the current DWIM logic is helpful, really.
Yet AFAICT the kill-ring logic was there already when the clipboard
logic was added, so I'm not sure the duplication is completely redundant.
Stefan
next prev parent reply other threads:[~2021-07-05 15:59 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-06-21 14:29 bug#27442: Un-obsolete x-clipboard-yank, or provide analogous functional Constantine Kharlamov
2017-06-21 19:10 ` Eli Zaretskii
2017-06-21 19:55 ` Constantine Kharlamov
2021-07-05 14:13 ` Lars Ingebrigtsen
2021-07-05 14:46 ` Stefan Monnier via Bug reports for GNU Emacs, the Swiss army knife of text editors
2021-07-05 15:28 ` Lars Ingebrigtsen
2021-07-05 15:59 ` Stefan Monnier via Bug reports for GNU Emacs, the Swiss army knife of text editors [this message]
2021-07-05 16:55 ` Eli Zaretskii
2021-07-05 20:11 ` Lars Ingebrigtsen
2021-07-05 20:24 ` Lars Ingebrigtsen
2021-07-06 11:21 ` Eli Zaretskii
2021-07-06 14:18 ` Lars Ingebrigtsen
2021-07-06 15:45 ` Eli Zaretskii
2021-07-06 16:20 ` Lars Ingebrigtsen
2021-07-06 17:15 ` Eli Zaretskii
2021-07-06 17:26 ` Lars Ingebrigtsen
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=jwv7di4ycwz.fsf-monnier+emacs@gnu.org \
--to=bug-gnu-emacs@gnu.org \
--cc=27442@debbugs.gnu.org \
--cc=Hi-Angel@yandex.ru \
--cc=eliz@gnu.org \
--cc=larsi@gnus.org \
--cc=monnier@iro.umontreal.ca \
/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).