From mboxrd@z Thu Jan 1 00:00:00 1970 From: Neil Jerram Subject: Re: [RFC] Fixing link encoding once and for all Date: Thu, 28 Feb 2019 10:24:26 +0000 Message-ID: References: <87tvguyohn.fsf@nicolasgoaziou.fr> <87sgw9cxr8.fsf@nicolasgoaziou.fr> Mime-Version: 1.0 Content-Type: text/plain; charset="UTF-8" Return-path: Received: from eggs.gnu.org ([209.51.188.92]:56359) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1gzIro-00031n-5c for emacs-orgmode@gnu.org; Thu, 28 Feb 2019 05:24:40 -0500 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1gzIrn-0007vn-GE for emacs-orgmode@gnu.org; Thu, 28 Feb 2019 05:24:40 -0500 Received: from mail-lj1-x231.google.com ([2a00:1450:4864:20::231]:39959) by eggs.gnu.org with esmtps (TLS1.0:RSA_AES_128_CBC_SHA1:16) (Exim 4.71) (envelope-from ) id 1gzIrn-0007vV-7t for emacs-orgmode@gnu.org; Thu, 28 Feb 2019 05:24:39 -0500 Received: by mail-lj1-x231.google.com with SMTP id w6so16623537ljd.7 for ; Thu, 28 Feb 2019 02:24:38 -0800 (PST) In-Reply-To: <87sgw9cxr8.fsf@nicolasgoaziou.fr> 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" To: Neil Jerram , Org Mode List On Wed, 27 Feb 2019 at 10:49, Nicolas Goaziou wrote: > > Hello, > > Neil Jerram writes: > > > I'm not sure how much freedom you have here, but I think it would be > > both clearer - by avoiding confusion with URL-escaping - and easier to > > type, to use an entirely different form of escaping in the Org syntax; > > probably just this: > > > > \[ and \] to include a square bracket in a link > > \\ to include a backslash > > Wouldn't that become problematic with file names in Windows? Do you mean Windows file names in existing Org files? I.e. the back-compatibility concern? If so, yes, I confess I didn't think at all about back-compatibility, with my suggestion above. So perhaps that rules my idea out. If we were starting from scratch, however, - I believe it would technically be fine; i.e. it's a complete and unambiguous encoding - it might be considered awkward for Windows users to have to write c:\\system32\\mydoc.txt instead of c:\system32\mydoc.txt, but I don't know how big a concern that would be. Best wishes, Neil > Regards, > > -- > Nicolas Goaziou