emacs-orgmode
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[BUG] URI handling is overly complicated and nonstandard [9.6.7 (N/A @ /


From: Max Nikulin
Subject: [BUG] URI handling is overly complicated and nonstandard [9.6.7 (N/A @ /gnu/store/mg7223g8mw90lccp6mm5g6f3mpjk70si-emacs-org-9.6.7/share/emacs/site-lisp/org-9.6.7/)]
Date: Sat, 2 Sep 2023 19:00:43 +0700
User-agent: Mozilla/5.0 (X11; Linux x86_64; rv:102.0) Gecko/20100101 Thunderbird/102.14.0

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 feature, but anyway it does not work as expected.

  (org-link-set-parameters "tel")

or

  (org-link-set-parameters
   "tel"
   :export (lambda (_path _descr _backend) nil))

strips link type and exports links as e.g.

  \href{321}{call}

"tel:" is missed. Each backend has its own hardcoded list of blessed link types to preserve link type/protocol/scheme:
- LaTeX: "http" "https" "ftp" "mailto" "doi"
- HTML:  "http" "https" "ftp" "mailto" "news"

Actually I had in mind more flexible delegation. :export functions should be able to alter URI, attributes and to provide description if it is missed, but did not care if '<a href=""></a>' or '\href{}{}' should be used.

Easy way to add protocol/scheme should include :follow with `browse-url' as well.




reply via email to

[Prev in Thread] Current Thread [Next in Thread]