On 05/09/2023 16:42, Ihor Radchenko wrote:
Max Nikulin writes:
From my point of view it will be more sane behavior. However it may
require update of 3rd party ox backends.
Yes. The main problem is that I fail to understand the motivation behind
the current behaviour. git logs reveal that the code is there from the
initial version of the library.
Just a guess, likely unrelated to actual decision. For links like
"lisp:" or "shell:" keeping link type does not have much sense (however
stripping it is questionable as well).
From my point of view, e.g. <elisp:(identity "a")> should be exported
as plain text <code>(identity "a")</code> rather than an (invalid due to
not escaped quotes inside href) link <a href="(identity "a")">(identity
"a")</a>.
I still believe that fallback export should preserve link type. Code
links should define their export functions.
