From: Sebastian Rose <sebastian_rose@gmx.de>
To: Tassilo Horn <tassilo@member.fsf.org>
Cc: emacs-orgmode@gnu.org
Subject: Re: Re: org-protocol://remember:// question
Date: Sat, 04 Apr 2009 15:39:23 +0200 [thread overview]
Message-ID: <877i20ler8.fsf@kassiopeya.MSHEIMNETZ> (raw)
In-Reply-To: <873acowy9b.fsf@thinkpad.tsdh.de> (Tassilo Horn's message of "Sat, 04 Apr 2009 11:42:40 +0200")
Tassilo Horn <tassilo@member.fsf.org> writes:
> But one question remains. Do I have to do some special quoting in order
> to allow the protocol to split URL, TITLE and TEXT correctly? Let's say
> I do
>
> emacsclient -c \
> 'org-protocol:/remember:/http://www.google.de/the search engine/bla fasel bla'
>
> the link (%c) looks like [[http:][www.google.de]] which in not quite
> correct.
Yes. The best is to URL-encode the fields.
The slash is used as field separator for the following reason:
emacsclient compresses double or tripple slashes to one ("//" -> "/"),
which means those double slashes won't survive a call.
http://www.google.de/the search engine/
would become
http:/www.google.de/the search engine/
Hence we must encode slashes anyway. Double slashes are quite common on
web pages and could also reside in their titles.
But you could use any string as separator in custom handlers.
Best,
Sebastian
next prev parent reply other threads:[~2009-04-04 13:36 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-04-02 6:50 org-protocol://remember:// question Tassilo Horn
2009-04-02 11:10 ` Sebastian Rose
2009-04-02 12:28 ` Sebastian Rose
2009-04-02 16:03 ` Carsten Dominik
2009-04-02 16:03 ` Carsten Dominik
2009-04-02 18:00 ` Sebastian Rose
2009-04-03 7:47 ` Carsten Dominik
2009-04-03 12:06 ` Sebastian Rose
2009-04-03 12:34 ` Sebastian Rose
2009-04-03 16:58 ` Carsten Dominik
2009-04-03 22:59 ` Sebastian Rose
2009-04-04 9:42 ` Tassilo Horn
2009-04-04 13:39 ` Sebastian Rose [this message]
2009-04-04 17:36 ` Tassilo Horn
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=877i20ler8.fsf@kassiopeya.MSHEIMNETZ \
--to=sebastian_rose@gmx.de \
--cc=emacs-orgmode@gnu.org \
--cc=tassilo@member.fsf.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 external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.