From: Ihor Radchenko <yantar92@gmail.com>
To: chris <inkbottle007@gmail.com>
Cc: emacs-orgmode@gnu.org
Subject: Re: cut and paste not working after xdg-open "org-protocol://store-link?url=URL&title=TITLE"
Date: Sun, 30 Jan 2022 11:36:01 +0800 [thread overview]
Message-ID: <871r0px5cu.fsf@localhost> (raw)
In-Reply-To: <3701125.3ICyicTkgz@pluto>
chris <inkbottle007@gmail.com> writes:
> 3- if you do `C-y` you can see the URL is in the kill-ring
> But obviously there is no reason for this URL to be also in the Wayland (or
> x11) clipboard? (there is no law of nature saying that what is in emacs kill-
> ring must necessarily also be in wayland clipboard. I think there is a law of
> nature for the other way around though)
> In any case, in the case of Kde/Kwin/Wayland, it is not copied in the Wayland
> clipboard.
> Maybe it's in the description of org-protocol/store-link that the URL should
> be copied in emacs kill-ring, in any case, it is.
> But no it doesn't show in the kde/wayland clipboard (and why would it).
I am not 100% sure if I understand your message clearly. However, just
letting you know about existence of the following Emacs customisations:
save-interprogram-paste-before-kill:
Whether to save existing clipboard text into kill ring before replacing it.
select-enable-primary:
Non-nil means cutting and pasting uses the primary selection.
Best,
Ihor
next prev parent reply other threads:[~2022-01-30 3:38 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-01-27 0:03 cut and paste not working after xdg-open "org-protocol://store-link?url=URL&title=TITLE" chris
2022-01-28 12:40 ` Max Nikulin
2022-01-30 3:12 ` chris
2022-01-30 3:36 ` Ihor Radchenko [this message]
2022-01-30 18:38 ` chris
2022-01-31 1:14 ` Ihor Radchenko
2022-01-31 2:13 ` chris
2022-01-31 3:28 ` Ihor Radchenko
2022-01-31 3:43 ` chris
2022-01-31 3:49 ` chris
2022-01-31 4:00 ` chris
2022-01-31 6:47 ` Tim Cross
2022-01-31 16:29 ` Max Nikulin
2022-02-01 5:48 ` chris
2022-02-01 5:57 ` chris
2022-02-02 16:49 ` Max Nikulin
2022-01-30 8:31 ` Max Nikulin
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.orgmode.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=871r0px5cu.fsf@localhost \
--to=yantar92@gmail.com \
--cc=emacs-orgmode@gnu.org \
--cc=inkbottle007@gmail.com \
/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/org-mode.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).