[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [O] org-protocol-capture and chrome

From: Harri Kiiskinen
Subject: Re: [O] org-protocol-capture and chrome
Date: Thu, 19 Apr 2012 23:20:02 +0300 (EEST)

From: Richard Riley <address@hidden>
Subject: Re: [O] org-protocol-capture and chrome
Date: Tue, 17 Apr 2012 12:06:32 +0200

> Richard Riley <address@hidden> writes:
>> Could someone please post a working setup (browser bookmark url and
>> template) for org-protocol-capture to correctly get triggered from a
>> Google Chrome bookmark link in order to store the current url. Googling
>> shows some conflicting views : some with removing calls to encodeURI and
>> others hacking xdg-open.


I just spent some time in trying to set this up last weekend. In
short, on linux, it does not work by default, as Chrome insists on
using the OS to open the link, more specifically gvfs-open. This
program, on the other hand, has a long-standing bug which makes it
unable to handle encoded URI's. If the URI is fed to it unencoded,
then org-protocol is not able to separate the different parts of the
argument as it uses internally '/' as separator.

I posted last week-end a patch to this list which adds a variable to
org-protocol to use a custom separator. In this case, the URI in
Chrome does not need to be encoded, and gvfs-open won't choke on it. I
found that a separator like '|||' works perfectly. With this patch,
the wiki examples work well, just leave out the

It feels stupid to add a custom variable just to circumvent this
problem, but the bug in gvfs-open was first reported in something like
2006 and still isn't fixed, so I guess it may not be something to hold
one's breath on.

The format of the patch was probably not correct as I have no idea
whether it made it anywhere from this list, but should be found in the
archives around April 14th.


Harri K.

reply via email to

[Prev in Thread] Current Thread [Next in Thread]