From: Sebastian Rose <sebastian_rose@gmx.de>
To: "Mattias Jämting" <mattias@jwd.se>
Cc: emacs-orgmode <emacs-orgmode@gnu.org>
Subject: Re: Org-protocol / Chrome on Linux
Date: Thu, 30 Sep 2010 17:56:17 +0200 [thread overview]
Message-ID: <87aamzrzry.fsf@gmx.de> (raw)
In-Reply-To: <87hbh7s0da.fsf@gmx.de> (Sebastian Rose's message of "Thu, 30 Sep 2010 17:43:29 +0200")
Sebastian Rose <sebastian_rose@gmx.de> writes:
> Mattias Jämting <mattias@jwd.se> writes:
>> Yes i'm running a pretty standard Ubuntu 10.04 setup.
>>
>> I managed to get it working on chrome by removing the
>> encodeURIComponent command on location.href.
>>
>> I could simulate it in the terminal like this.
>>
>> mattias@helium:~$ xdg-open org-protocol://capture://http%3A%2F%2Forgmode.org
>> Error showing URL: Operation not supported
>> mattias@helium:~$ xdg-open org-protocol://capture://http://orgmode.org
>> mattias@helium:~$ (worked)
>>
>> Strange that it worked in FF. Maybe Chrome and FF encodes URIs differently?
>
>
> Ooops!
>
> I just was going to blame Google.
>
> Looking into the ECMA standard, I found this:
>
> 15.1.3 URI Handling Function Properties
>
> ... ...
>
> A URI is composed of a sequence of components separated by
> component separators. The general form
> is:
> Scheme : First / Second ; Third ? Fourth
>
> where the italicised names represent components and the “:”, “/”,
> “;” and “?” are reserved characters used as separators. The
> encodeURI and decodeURI functions are intended to work with
> complete URIs; they assume that any reserved characters in the
> URI are intended to have special meaning and so are not
> encoded. The encodeURIComponent and decodeURIComponent functions
> are intended to work with the individual component parts of a
> URI; they assume that any reserved characters represent text and
> so must be encoded so that they are not interpreted as reserved
> characters when the component is part of a complete URI.
>
>
> That document states "encodeURI" is to be used with complete URIs (as
> the name says...). Funny. Chrome is the only browser that works like
> that :)
>
> I'll go and adjust the docs.
>
>
> Thanks for your Report!!
>
Actually --- errr --- there is nothing to adjust. The docs are exactly
right.
This is because of some örfflkjsgs in xdg-open.
No one ever said something about xdg-open. Org-protocol is supposed to
work with emacsclient:
mattias@helium:~$ emacsclient org-protocol://capture://http%3A%2F%2Forgmode.org
works.
Sebastian
next prev parent reply other threads:[~2010-09-30 15:56 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-08-31 17:20 Org-protocol / Chrome on Linux Mattias Jämting
2010-08-31 23:20 ` Sebastian Rose
2010-09-30 13:11 ` Mattias Jämting
2010-09-30 15:43 ` Sebastian Rose
2010-09-30 15:56 ` Sebastian Rose [this message]
2010-11-24 23:23 ` Mattias Jämting
2010-12-10 6:44 ` Ross Patterson
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=87aamzrzry.fsf@gmx.de \
--to=sebastian_rose@gmx.de \
--cc=emacs-orgmode@gnu.org \
--cc=mattias@jwd.se \
/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).