Hello,
Michael Brand writes:
>>This prevent any link with a description to contain either "]]" or
>
> ... a single bracket at the border or a link destination part to
> contain "][" or "]]" or a single bracket at the border or ...
Correct.
>>multiple spaces, but these requirements are
Hi Nicolas
Your suggestions are so convincing in going so far, I hope I
understand them right. If yes it is just thinking in terms of "[[",
"][" and "]]" instead of single brackets that I got used to with the
current escaping and unescaping in Org.
On Mon, Jul 25, 2016 at 2:52 PM, Nicolas Goaziou
Hello,
Michael Brand writes:
> There seems to be a related issue with an inconsistency between HTML
> and other export formats in using org-link-unescape for the link
> _destination_ part: With the Org file
>
> 1) https://duckduckgo.com/?q=Org+mode+%252B+Worg
> 2) https://duckduckgo.com/?q=Org+m
Hi Nicolas
There seems to be a related issue with an inconsistency between HTML
and other export formats in using org-link-unescape for the link
_destination_ part: With the Org file
1) https://duckduckgo.com/?q=Org+mode+%252B+Worg
2) https://duckduckgo.com/?q=Org+mode+%2B+Worg
org-open-at-point
Hello,
Arun Isaac writes:
> For external links without a description, `org-html-link' resuses the
> `path' as the inner text of the exported element. However, the
> `path' variable contains the URL encoded version of the `raw-path'. It
> would be more appropriate to put the actual unescaped uni
For external links without a description, `org-html-link' resuses the
`path' as the inner text of the exported element. However, the
`path' variable contains the URL encoded version of the `raw-path'. It
would be more appropriate to put the actual unescaped unicode URL in the
inner text of the e
