Max Nikulin <[email protected]> writes:
>> As a user, I would expect
>>
>> [[elisp:(identity "a")]]
>>
>> to be export-equivalent to
>>
>> src_elisp[:exports code]{(identity "a")}
>>
>> across all backends.
Makes sense.
>>> What is your expectation for links having description?
>>>
>>> [[elisp:(identity "a")][Run it]]
>>
>> Good point! Perhaps we just need to find a
>> good symbol that would work well between the
>> Elisp code and the description?
>>
>> For example
>>
>> /Run it/ \to src_elisp[:exports code]{(identity "a")}
>>
>> exports to ASCII as
>>
>> /Run it/ -> `(identity "a")'
>>
>> Of course, \to could be something else...
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.
--
Ihor Radchenko // yantar92,
Org mode contributor,
Learn more about Org mode at <https://orgmode.org/>.
Support Org development at <https://liberapay.com/org-mode>,
or support my work at <https://liberapay.com/yantar92>
