Hello, Fabrice Popineau <fabrice.popin...@supelec.fr> 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
