[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [O] [RFC] Fixing link encoding once and for all
From: |
Nicolas Goaziou |
Subject: |
Re: [O] [RFC] Fixing link encoding once and for all |
Date: |
Fri, 01 Mar 2019 09:14:06 +0100 |
User-agent: |
Gnus/5.13 (Gnus v5.13) Emacs/26.1 (gnu/linux) |
Hello,
Neil Jerram <address@hidden> writes:
> 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.
Thinking a bit more about it, we don't need to escape /all/ square
brackets, only "]]" and "][" constructs. Therefore, we don't need to
escape every backslash either.
The regexp for bracket links could be, in its simple (!) form:
\[\[\(.*?[^\\]\(?:\\\)*\)\]\(?:\[\([^\000]+?\)\]\)?\]
Most links would need no change. I see one notable exception:
directories in Windows:
[[c:\system32\\]] for "c:\system32\"
Some further notes:
1. Macros already use backslashes to escape commas in arguments, so it
is at least consistent with this part of Org.
2. The description part of the link, like most parts of Org, does not
use backslash escaping. If needed, we can implement an entity for
a square bracket.
3. There will be some backward compatibility issues. We can add
a checker in Org Lint to catch most of those. For example, we could
look at URI where every percent is followed only by 25, 5B, and 5D.
WDYT?
Regards,
--
Nicolas Goaziou
- Re: [O] [RFC] Fixing link encoding once and for all,
Nicolas Goaziou <=
- Re: [O] [RFC] Fixing link encoding once and for all, Nicolas Goaziou, 2019/03/01
- Re: [O] [RFC] Fixing link encoding once and for all, Michael Brand, 2019/03/01
- Re: [O] [RFC] Fixing link encoding once and for all, Jens Lechtenboerger, 2019/03/01
- Re: [O] [RFC] Fixing link encoding once and for all, stardiviner, 2019/03/03
- Re: [O] [RFC] Fixing link encoding once and for all, Neil Jerram, 2019/03/04