From: Michael Dauer <mick.dauer@gmail.com>
To: Ihor Radchenko <yantar92@posteo.net>
Cc: emacs-orgmode@gnu.org
Subject: Re: BUG: org-protocol broken
Date: Tue, 1 Aug 2023 15:38:59 +0200 [thread overview]
Message-ID: <CAP7OBxJF2G7jWZAfF2BE5P1+OXGjwOzzRgQt5MF91AporQCPeA@mail.gmail.com> (raw)
In-Reply-To: <87bkfrotsn.fsf@localhost>
[-- Attachment #1: Type: text/plain, Size: 1139 bytes --]
Just look at the first examples, which are 1-to-1 copied from org-protocol
code/documentation.
org-protocol://store-link?url=foo&title=bar
is not working. And this is exactly what store-link is for.
Am Di., 1. Aug. 2023 um 14:01 Uhr schrieb Ihor Radchenko <
yantar92@posteo.net>:
> Michael Dauer <mick.dauer@gmail.com> writes:
>
> > emacsclient "org-protocol://store-link?url=http:123&title=t: w: q&a - r-s
> > (a)"
> > shows *ERROR*: Wrong type argument: arrayp, nil
> >
> > IMO the last example is a fully plausible link. I actually need it to
> > create a link which then calsl e.g. the outlook protocol.
>
> "&" in title is ambiguous - it interferes with "&" in the protocol URI
> scheme. You need to URL-encode "&" to escape the "&" that are actually
> parts of key values.
>
> > ~2 months ago the same links worked fine.
>
> We did not have any significant changes in org-protocol for years.
>
> --
> Ihor Radchenko // yantar92,
> Org mode contributor,
> Learn more about Org mode at <https://orgmode.org/>.
> Support Org development at <https://liberapay.com/org-mode>,
> or support my work at <https://liberapay.com/yantar92>
>
[-- Attachment #2: Type: text/html, Size: 1945 bytes --]
next prev parent reply other threads:[~2023-08-01 13:40 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-08-01 11:44 BUG: org-protocol broken Michael Dauer
2023-08-01 12:01 ` Ihor Radchenko
2023-08-01 13:38 ` Michael Dauer [this message]
2023-08-01 13:40 ` Michael Dauer
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=CAP7OBxJF2G7jWZAfF2BE5P1+OXGjwOzzRgQt5MF91AporQCPeA@mail.gmail.com \
--to=mick.dauer@gmail.com \
--cc=emacs-orgmode@gnu.org \
--cc=yantar92@posteo.net \
/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).