emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: chris <inkbottle007@gmail.com>
To: emacs-orgmode@gnu.org
Subject: cut and paste not working after xdg-open "org-protocol://store-link?url=URL&title=TITLE"
Date: Thu, 27 Jan 2022 01:03:08 +0100	[thread overview]
Message-ID: <1902025.jDVfpnRRgo@pluto> (raw)

[-- Attachment #1: Type: text/plain, Size: 1575 bytes --]

Hi people,


First: `xdg-open "org-protocol://store-link?url=URL&title=TITLE"` from a terminal.
Then `M-x org-insert-link` in emacs, or not (it makes no difference).
Then cut-and-paste from non-emacs-application (e.g., Kde's Konsole, or Firefox) to emacs.
When doing `C-y` what it pastes is "URL", not what I have copied from Firefox.
For it to work again: one cut-and-paste operation from emacs to emacs.
Then it works again until the next time.
Doing `C-k` is enough, but it's still cumbersome.


My compositor is Wayland. It was like this, before, with `emacs-pgtk` 28.0.50.
It is still like that with: GNU Emacs 29.0.50 (build 1, x86_64-pc-linux-gnu, GTK+ Version 
3.24.31, cairo version 1.16.0) of 2022-01-26
System is debian sid upgraded just before.


Thanks,
Chris


PS: some XY-problem:
What sort of argument to pass to `org-protocol-store-link`.
When I do `(org-protocol-parse-parameters "url=U&title=T" t '(:url :title))` it works.
It works when I do `xdg-open "org-protocol://store-link?url=URL&title=TITLE"
` from a terminal.
But why is there a `nil` here:
https://github.com/emacs-mirror/emacs/blob/19dcb237/lisp/org/org-protocol.el#L467[1]
And why is it working at all from `xdg-open "org-protocol://store-link?
url=URL&title=TITLE"`, with a `nil` in that position?


Note: `(org-protocol-store-link "U/T")` works, `(org-protocol-store-link "url=U&title=T")` 
doesn't work. Produces link `[[url=U&title=T]]` instead of `[[U][T]]`.

--------
[1] https://github.com/emacs-mirror/emacs/blob/
19dcb237b5b02b36580294ab309124f346a66024/lisp/org/org-protocol.el#L467

[-- Attachment #2: Type: text/html, Size: 3854 bytes --]

             reply	other threads:[~2022-01-27  0:03 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-01-27  0:03 chris [this message]
2022-01-28 12:40 ` cut and paste not working after xdg-open "org-protocol://store-link?url=URL&title=TITLE" Max Nikulin
2022-01-30  3:12   ` chris
2022-01-30  3:36     ` Ihor Radchenko
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=1902025.jDVfpnRRgo@pluto \
    --to=inkbottle007@gmail.com \
    --cc=emacs-orgmode@gnu.org \
    /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).