Re: Exporting elisp: and shell: links

[Max Nikulin]

On 23/09/2023 06:43, Rudolf Adamkovič wrote:
> Ihor Radchenko writes:
>
> > Another idea: use code as description displayed in the tooltip (in html).
> > Copy-on-clip also makes sense.
> >
> > Yet another idea: export code inside a footnote. This will work across
> > all the backends.
>
> Yet another, another idea: export the description as a Lisp comment,
> after converting it to plain text.  To use Max's example:
>
> src_elisp[:exports code]{(server-start) ; Launch server}
> src_elisp[:exports code]{(server-start) ; `M-x server-start RET'}

I do not think, code with comments is suitable for inline source blocks, 
such code should occupy a dedicated line.

I am afraid, there is no variant that fits for all cases even in a 
particular document. It would be great to mark specific links, which way 
each one should be exported:

    You should run
    <attr:(:omit-code t)>[[elisp:(server-start)][=M-x server-start=]].
    Or you can [[elisp:(identity "a")][run it]].

    <p>You should run
    <code data-org-link="(server-start)">M-x server-start</code>.
    Or you can <span class="eval-link">run it</span> ->
    <code>(identity "a")</code>.

I know, Ihor do not like the idea of attributes for inline objects
due to complexity of current implementation of parser for #+attr_html:

Ihor Radchenko. Re: [HELP] Fwd: Org format as a new standard source 
format for GNU manuals. Mon, 03 Oct 2022 12:36:20 +0800. 
https://list.orgmode.org/87r0zpy14r.fsf@localhost