Ihor Radchenko writes:
>> I still believe that fallback export should preserve link type. Code
>> links should define their export functions.
>
> Let's get started on tackling this problem from not stripping the link
> type.
>
> I am attaching tentative patch to that effect, as a first step.
Ap
Max Nikulin writes:
> 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
Max Nikulin writes:
> From my point of view, e.g. should be exported
> as plain text (identity "a") rather than an (invalid due to
> not escaped quotes inside href) link (identity
> "a").
This would be a very welcome fix! I avoid
'elisp' links, even in my Emacs notes, as
they do not export
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 th
Max Nikulin writes:
>>> (org-link-set-parameters "tel")
> ...
>>> \href{321}{call}
>>>
>>> "tel:" is missed.
>
> I have realized that it is possible to take advantage of current behavior:
>
>(org-link-set-parameters
> "browse"
> :follow
> (lambda (url arg) (browse-url url
On 03/09/2023 14:53, Ihor Radchenko wrote:
Max Nikulin writes:
I missed this feature, but anyway it does not work as expected.
(org-link-set-parameters "tel")
...
\href{321}{call}
"tel:" is missed.
I have realized that it is possible to take advantage of current behavior:
(org-l
Max Nikulin writes:
> On 01/09/2023 16:04, Ihor Radchenko wrote:
>> Max Nikulin writes:
>>
>>> However I do not mind to have an easy way to delegate URI from :export
>>> function to the link transcoder of active export backend.
>
>> Just make the :export function return nil.
>
> I missed this fe
On 31/08/2023 22:25, Csepp wrote:
There seems to be no easy way to tell it
to just treat it the same way it would treat an HTTP link and include it
verbatim. There does seem to be a way to do some Elisp scripting, but
it's honestly really annoying to do this for every protocol type.
Please, jus
