From mboxrd@z Thu Jan 1 00:00:00 1970 From: "Mark E. Shoulson" Subject: Spaces in bare URLs? Date: Tue, 17 Mar 2020 22:14:01 -0400 Message-ID: <78f598f3-44e1-63aa-751a-49c2f7208fe7@kli.org> Mime-Version: 1.0 Content-Type: text/html; charset=utf-8 Content-Transfer-Encoding: quoted-printable Return-path: Received: from eggs.gnu.org ([2001:470:142:3::10]:35208) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1jEODb-0004xa-Mi for emacs-orgmode@gnu.org; Tue, 17 Mar 2020 22:14:04 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1jEODa-0004qg-Jv for emacs-orgmode@gnu.org; Tue, 17 Mar 2020 22:14:03 -0400 Received: from pi.meson.org ([96.56.207.26]:47084) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1jEODa-0004i3-FN for emacs-orgmode@gnu.org; Tue, 17 Mar 2020 22:14:02 -0400 Received: from nagas.meson.org (nagas [192.168.2.101]) (using TLSv1.3 with cipher TLS_AES_128_GCM_SHA256 (128/128 bits) key-exchange X25519 server-signature RSA-PSS (2048 bits) server-digest SHA256) (No client certificate requested) by pi.meson.org (Postfix) with ESMTPS id 9C4FD220418 for ; Tue, 17 Mar 2020 22:14:01 -0400 (EDT) Content-Language: en-US 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-mx.org@gnu.org Sender: "Emacs-orgmode" To: org-mode mailing list

So, in the "new" org-mode, we've done away with standard percent-encoding of URLs, in favor of a more... idiosyncratic method using backslashes.=C2=A0 So... what is one supposed to do ab= out spaces in URLs?=C2=A0 When they're in [[link format]], with or with= out a description, it's no problem, but org-mode has a long tradition of support for "bare" URLs too.=C2=A0 We're used to being able to t= ype a URL or other link format and have it work, right?=C2=A0 And that doesn't seem (to me) to be a thing that we'd want to abandon.

In org-mode 9.1.9, I can type "info:elisp#Syntactic%20Font%20Lock" and it'd work.=C2=A0= (Maybe not the greatest example, since %-encoding is seen more with http-based URIs, but still).=C2=A0 The percent-encoding is well-established and reliable, and you can *count* on it when nothing else works, because you can always fall back on plain ascii.=C2=A0 But that won't work in org-mode 9.3.6.=C2=A0 Nor will "info:elisp#Syntactic Font Lock" or "info:elisp#Syntactic\ Fo= nt\ Lock" or any other variant I've tried, short of putting it insi= de [[]]s or <>s (in other words, no longer using a bare URL).

I think dropping percent-escaping of URLs was a bad idea, in terms of breaking past usage and lack of consistency with the standard used for URLs everywhere else.=C2=A0 But I don't know what impelled the decision to drop it, so I might well be missing something important.=C2=A0 At any rate, it does leave a hole in wha= t org-mode can do, a thing it used to be able to do and can't anymore.=C2=A0 Is there a right way to do this?=C2=A0 (without usin= g delimiters.)

I haven't yet looked at how this interacts with org-protocol's store-link transaction.

~mark