From mboxrd@z Thu Jan 1 00:00:00 1970 From: Sebastian Rose Subject: Re: Re: org-protocol://remember:// question Date: Sat, 04 Apr 2009 15:39:23 +0200 Message-ID: <877i20ler8.fsf@kassiopeya.MSHEIMNETZ> References: <87ocvfh7lc.fsf@thinkpad.tsdh.de> <87k561tkba.fsf@kassiopeya.MSHEIMNETZ> <873acowy9b.fsf@thinkpad.tsdh.de> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Return-path: Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1Lq62e-0003di-42 for emacs-orgmode@gnu.org; Sat, 04 Apr 2009 09:36:12 -0400 Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1Lq62Z-0003VI-8M for emacs-orgmode@gnu.org; Sat, 04 Apr 2009 09:36:11 -0400 Received: from [199.232.76.173] (port=50989 helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1Lq62Z-0003V5-4h for emacs-orgmode@gnu.org; Sat, 04 Apr 2009 09:36:07 -0400 Received: from mail.gmx.net ([213.165.64.20]:51771) by monty-python.gnu.org with smtp (Exim 4.60) (envelope-from ) id 1Lq62Y-0003jM-J3 for emacs-orgmode@gnu.org; Sat, 04 Apr 2009 09:36:07 -0400 In-Reply-To: <873acowy9b.fsf@thinkpad.tsdh.de> (Tassilo Horn's message of "Sat, 04 Apr 2009 11:42:40 +0200") List-Id: "General discussions about Org-mode." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: emacs-orgmode-bounces+geo-emacs-orgmode=m.gmane.org@gnu.org Errors-To: emacs-orgmode-bounces+geo-emacs-orgmode=m.gmane.org@gnu.org To: Tassilo Horn Cc: emacs-orgmode@gnu.org Tassilo Horn writes: > But one question remains. Do I have to do some special quoting in order > to allow the protocol to split URL, TITLE and TEXT correctly? Let's say > I do > > emacsclient -c \ > 'org-protocol:/remember:/http://www.google.de/the search engine/bla fasel bla' > > the link (%c) looks like [[http:][www.google.de]] which in not quite > correct. Yes. The best is to URL-encode the fields. The slash is used as field separator for the following reason: emacsclient compresses double or tripple slashes to one ("//" -> "/"), which means those double slashes won't survive a call. http://www.google.de/the search engine/ would become http:/www.google.de/the search engine/ Hence we must encode slashes anyway. Double slashes are quite common on web pages and could also reside in their titles. But you could use any string as separator in custom handlers. Best, Sebastian