From mboxrd@z Thu Jan 1 00:00:00 1970 From: Harri Kiiskinen Subject: Re: org-protocol-capture and chrome Date: Thu, 19 Apr 2012 23:20:02 +0300 (EEST) Message-ID: <20120419.232002.485672597.harkiisk@gmail.com> References: <18hawiisev.fsf@news.eternal-september.org> Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Content-Transfer-Encoding: 7bit Return-path: Received: from eggs.gnu.org ([208.118.235.92]:46575) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1SKxpr-0006Zc-Cg for emacs-orgmode@gnu.org; Thu, 19 Apr 2012 16:20:12 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1SKxpp-000797-Iu for emacs-orgmode@gnu.org; Thu, 19 Apr 2012 16:20:10 -0400 Received: from mail-lpp01m010-f41.google.com ([209.85.215.41]:44540) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1SKxpp-00073s-9N for emacs-orgmode@gnu.org; Thu, 19 Apr 2012 16:20:09 -0400 Received: by lagz14 with SMTP id z14so7777632lag.0 for ; Thu, 19 Apr 2012 13:20:06 -0700 (PDT) In-Reply-To: <18hawiisev.fsf@news.eternal-september.org> List-Id: "General discussions about Org-mode." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: emacs-orgmode-bounces+geo-emacs-orgmode=m.gmane.org@gnu.org Sender: emacs-orgmode-bounces+geo-emacs-orgmode=m.gmane.org@gnu.org To: emacs-orgmode@gnu.org, rileyrg@gmail.com 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 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.