[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [O] Escaping links
From: |
Nicolas Goaziou |
Subject: |
Re: [O] Escaping links |
Date: |
Sat, 19 Aug 2017 11:15:25 +0200 |
User-agent: |
Gnus/5.13 (Gnus v5.13) Emacs/25.2 (gnu/linux) |
Hello,
Fabrice Popineau <address@hidden> writes:
> You could also prefix the link by a string holding (in ascii) the number of
> bytes of the unencoded link.
>
> But that makes raw/manual editing of an org file much harder.
I'd rather have something simple.
Here are some suggestions.
1. Replace "\\[\\[\\([^][]+\\)\\]\\(\\[\\([^][]+\\)\\]\\)?\\]"
(`org-bracket-link-regexp') with
"\\[\\[\\([^\000]+?\\)\\]\\(\\[\\([^\000]+?\\)\\]\\)?\\]". This gives
more possibilities. We will just live with the unsupported cases
(e.g. square brackets at the end of the path or the description).
2. Use good ole backslash character to escape ambiguous characters (even
though any character can be escaped). `org-link-unescape' would take
care of them instead of url-encoded characters.
3. A mix of both. `org-bracket-link-regexp' could become more
complicated though.
I'm open to other suggestions, as long as they do not massively impede
manual editing.
Regards,
--
Nicolas Goaziou
- [O] Escaping links, Fabrice Popineau, 2017/08/11
- Re: [O] Escaping links, Nicolas Goaziou, 2017/08/11
- Re: [O] Escaping links, John Kitchin, 2017/08/11
- Re: [O] Escaping links, Fabrice Popineau, 2017/08/11
- Re: [O] Escaping links, Nicolas Goaziou, 2017/08/12
- Re: [O] Escaping links, John Kitchin, 2017/08/12
- Re: [O] Escaping links, Neil Jerram, 2017/08/14
- Re: [O] Escaping links, Fabrice Popineau, 2017/08/14
- Re: [O] Escaping links,
Nicolas Goaziou <=