Re: [O] Accessing the communication channel from a link exporter

John Kitchin writes: > then the preprocessing hook sounds better. You can just replace the > links with generated html, and then export the buffer. > > For example, here is a function that goes through an org file and > replaces links that are file times with image or urls, and copies the > file

Re: [O] Accessing the communication channel from a link exporter

then the preprocessing hook sounds better. You can just replace the links with generated html, and then export the buffer. For example, here is a function that goes through an org file and replaces links that are file times with image or urls, and copies the file contents to a media-directory.

Re: [O] Accessing the communication channel from a link exporter

> I think this is the kind of thing you can use a filter for But, it gets more complicated than that. I have XMP metadata (license, caption, etc.) stored in the image files as well. And, in order to export that, I need the path to the source image file. So, my image link exporter needs the

Re: [O] Accessing the communication channel from a link exporter

I think this is the kind of thing you can use a filter for, or a function in the org-export-before-processing-hook to change the paths prior to export. Arun Isaac writes: >> Out of curiosity, what kind of link are you using, that is dependant >> about context ? > > Actually, I don't need the

Re: [O] Accessing the communication channel from a link exporter

> Out of curiosity, what kind of link are you using, that is dependant > about context ? Actually, I don't need the context of the link in the org document. I need some properties defined in the plist of the component in org-publish-project-alist. So, I use the info communication channel to

Re: [O] Accessing the communication channel from a link exporter

Hello, Arun Isaac writes: > When adding a new hyperlink type using `org-add-link-type', how do I > access the info communication channel from the link exporter function? You cannot. The :export link parameter is orthogonal to the export back-end. The latter only

[O] Accessing the communication channel from a link exporter

When adding a new hyperlink type using `org-add-link-type', how do I access the info communication channel from the link exporter function? Not being able to access the communication channel limits what I can do with `org-add-link-type', and I end up creating a derived backend with my own link