Exporting elisp: and shell: links

[Max Nikulin]

On 18/09/2023 05:08, Rudolf Adamkovič wrote:
> Max Nikulin writes:
>
> >  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>.
>
> This would be a very welcome fix!  I avoid
> 'elisp' links, even in my Emacs notes, as
> they do not export correctly.

Do you think a label specifying language should be added to code 
snippets, e.g. <code title="elisp">(identity "a")</code> or it is 
useless and may cause undesired noise for screen reader users? What 
about LaTeX?

What is your expectation for links having description?

  [[elisp:(identity "a")][Run it]]

Unsure if making plain text from description is the best solution. Some 
interactive element may be added to HTML to reveal the code or at least 
it may be put into tooltip <span class="code" title="elisp:(identity 
&quot;a&quot;)">Run it</span>. The downside is that title attribute can 
not be easily copied (at least without a dedicated extension). ODT and 
LaTeX are more tricky again (a footnote?).