From: Bernhard Schmitz <Bernhard.Schmitz@vis.uni-stuttgart.de>
To: "emacs-orgmode@gnu.org" <emacs-orgmode@gnu.org>
Subject: Exporting custom dynamic blocks
Date: Tue, 19 May 2015 14:58:46 +0000 [thread overview]
Message-ID: <ba64f73775244729bd8b4b7405ea7380@barcarole.visus.uni-stuttgart.de> (raw)
Hi,
What is the canonical way of exporting custom dynamic blocks? Is there a mechanism similar to org-dblock-write: only for exporting dblocks? I cannot find any documentation on this.
To give a little background to my question: I am currently writing a conversion from deadlines/schedules/effort to pgf-gantt charts. This was discussed before on this list, but I couldn't find anyone actually implementing it. (In case someone wants to try: https://github.com/HeyFlash/emacs-stuff/blob/master/experiments/org-gantt-experiment.el )
Ideally I would like to create a custom dynamic block that contains the result of my parsing and computation, and then have a custom exporter for that dynamic block that creates the pgf-gantt code, so that I can later add exporters for other formats, e.g. html.
If there is no such mechanism, what is the best way of storing that pgf-gantt source code so that it gets integrated into latex export, but doesn't interfere with other exporters? Currently I'm simply writing the pgf-gantt code into the custom block, and this does get exported correctly to latex, but produces boxes with error messages in html.
Thank you & regards,
Bernhard
next reply other threads:[~2015-05-19 14:59 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-05-19 14:58 Bernhard Schmitz [this message]
-- strict thread matches above, loose matches on Subject: below --
2015-05-19 13:22 Exporting custom dynamic blocks Bernhard Schmitz
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=ba64f73775244729bd8b4b7405ea7380@barcarole.visus.uni-stuttgart.de \
--to=bernhard.schmitz@vis.uni-stuttgart.de \
--cc=emacs-orgmode@gnu.org \
/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).