Bastien writes:
> Richard Riley writes:
>
>> Bernt Hansen writes:
>>
>>> Harri Kiiskinen writes:
>>>
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.
>>>
>>> It's
Richard Riley writes:
> Bernt Hansen writes:
>
>> Harri Kiiskinen writes:
>>
>>> 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.
>>
>> It's sitting on the patchwork serv
Bernt Hansen writes:
> Harri Kiiskinen writes:
>
>> 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.
>
> It's sitting on the patchwork server waiting to be dealt with.
>
> h
Harri Kiiskinen writes:
> 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.
It's sitting on the patchwork server waiting to be dealt with.
http://patchwork.newartisans.com/pro
From: Richard Riley
Subject: Re: [O] org-protocol-capture and chrome
Date: Tue, 17 Apr 2012 12:06:32 +0200
> Richard Riley writes:
>
>> Could someone please post a working setup (browser bookmark url and
>> template) for org-protocol-capture to correctly get triggered from
Richard Riley 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
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 x
