emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Harri Kiiskinen <harkiisk@gmail.com>
To: emacs-orgmode@gnu.org, rileyrg@gmail.com
Subject: Re: org-protocol-capture and chrome
Date: Thu, 19 Apr 2012 23:20:02 +0300 (EEST)	[thread overview]
Message-ID: <20120419.232002.485672597.harkiisk@gmail.com> (raw)
In-Reply-To: <18hawiisev.fsf@news.eternal-september.org>

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

> Richard Riley <rileyrg@gmail.com> 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.

Hi,

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
encodeRUIComponent-part.

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.

Best,

Harri K.

  reply	other threads:[~2012-04-19 20:20 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-04-17  8:55 org-protocol-capture and chrome Richard Riley
2012-04-17 10:06 ` Richard Riley
2012-04-19 20:20   ` Harri Kiiskinen [this message]
2012-04-20  1:23     ` Bernt Hansen
2012-04-20 10:22       ` Richard Riley
2012-04-20 10:48         ` Bastien
2012-04-20 11:42           ` Richard Riley

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=20120419.232002.485672597.harkiisk@gmail.com \
    --to=harkiisk@gmail.com \
    --cc=emacs-orgmode@gnu.org \
    --cc=rileyrg@gmail.com \
    /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).