Ihor Radchenko <yanta...@posteo.net> writes: > Joseph Turner <jos...@breatheoutbreathe.in> writes: > >> This change allows other packages to autoload their own link handlers. >> See this mu4e issue: >> >> https://github.com/djcb/mu/pull/2798 > >> +;;;###autoload >> (defun org-link-set-parameters (type &rest parameters) >> "Set link TYPE properties to PARAMETERS. >> PARAMETERS should be keyword value pairs. See > > Even though it would be useful to do such autoload, I cannot allow it. > This will unfortunately lead to annoying bugs we face every single major > Org release - mixing multiple Org versions. > > Because Elisp does not have a robust versioning of libraries, the > version of ol.el that will be used as a source of for > `org-link-set-parameters' will depend on the loading order of org > vs. mu4e in the user init. If mu4e is loaded early, running > `org-link-set-parameters' will trigger an autoload cookie for built-in > Org mode. Later, when packaged Org mode is loaded, things will get crazy > because of mixing multiple library versions and half-initialized variables. > > Canceled. > > Also, https://github.com/djcb/mu/pull/2798 will not work if Org is not > yet loaded when `package-initialize' is called.
Thank you for the explanation! Joseph
