From: Arun Isaac <arunisaac@systemreboot.net>
To: John Kitchin <jkitchin@andrew.cmu.edu>
Cc: org-mode-email <emacs-orgmode@gnu.org>
Subject: Re: Accessing the communication channel from a link exporter
Date: Fri, 02 Sep 2016 21:03:18 +0530 [thread overview]
Message-ID: <cu7a8fqwc3l.fsf@systemreboot.net> (raw)
In-Reply-To: <m2lgzascvp.fsf@Johns-MacBook-Air.local>
[-- Attachment #1: Type: text/plain, Size: 990 bytes --]
> 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 :base-directory to find the source image file. If I
try to get the XMP metadata from the published image file, then I
introduce a race condition with the export of the org file becoming
dependent on the image file already being published.
Perhaps, filters could be useful. I need to think about it. So far, I
have generally stayed away from filters because they can only get the
HTML as text, and have to use some kind of regex to operate on it. HTML
is structured data, and it would have been good if it was available in
some kind of S-form tree structure. It would have saved me the trouble
of parsing the HTML, and I could have used a library like xmlgen to
generate it.
Regards,
Arun Isaac
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 472 bytes --]
next prev parent reply other threads:[~2016-09-02 15:33 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-08-31 11:57 Accessing the communication channel from a link exporter Arun Isaac
2016-09-01 16:39 ` Nicolas Goaziou
2016-09-01 18:27 ` Arun Isaac
2016-09-02 12:30 ` John Kitchin
2016-09-02 15:33 ` Arun Isaac [this message]
2016-09-02 16:33 ` John Kitchin
2016-09-03 18:35 ` Arun Isaac
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://www.orgmode.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=cu7a8fqwc3l.fsf@systemreboot.net \
--to=arunisaac@systemreboot.net \
--cc=emacs-orgmode@gnu.org \
--cc=jkitchin@andrew.cmu.edu \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).