Max Nikulin <maniku...@gmail.com> writes: > `cons' is made an implementation detail, however completely opaque > structure is an obstacle for derived export backend. Perhaps getter > functions should be introduced as well.
I am looking at this again and the approach with special return values really feels like a kludge. What about passing an extra argument to :export function in `org-export-custom-protocol-maybe': (funcall protocol path desc backend info *link-object*) Then, if the :export function returns non-string, the return value is further processed as (org-export-data *return-value* info). This way, we can transparently return an https link in ol-man's `org-man-export' that will be handled automatically taking into account the ASCII inline note settings. All the existing export backends will continue working without modification. -- 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>
