From: Brett Viren <bv@bnl.gov>
To: Matt Lundin <mdl@imapmail.org>
Cc: Nick Dokos <ndokos@gmail.com>, emacs-orgmode@gnu.org
Subject: Re: Possible to use src block to generate org headlines for export?
Date: Wed, 23 Jul 2014 15:53:22 -0400 [thread overview]
Message-ID: <ir4r41bsvgt.fsf@lycastus.phy.bnl.gov> (raw)
In-Reply-To: <8761io2jnz.fsf@fastmail.fm> (Matt Lundin's message of "Wed, 23 Jul 2014 10:17:36 -0500")
[-- Attachment #1: Type: text/plain, Size: 1273 bytes --]
Matt Lundin <mdl@imapmail.org> writes:
> Brett Viren <bv@bnl.gov> writes:
>>
>> Maybe it would be more convenient to add the "meta-ness" you want as
>> part of a new exporter process?
>
> To change the "meta" wrappers for code block results, we would have to
> modify org babel (ob-core.el).
Just to be clear (hopefully) I actually meant something different. I
was suggesting to *not* use org babel to produce your extra headlines.
Rather, have whatever logic produces them reside in some new exporter.
I'm may be making incorrect guesses as to what you are actually going
for with these extra headlines. You mentioning this is for a blog made
me think they are some kind of "standard augmentation" for every blog
post or something. If not then I'm probably barking up the wrong tree.
But if so, putting them into an exporter seems apt.
This is an approach I'm taking in a JSON+HTML exporter (analogous to the
latex+pdf one) that I'm working on. For example, I'd like to have a
"tag cloud" generated from tags on org headlines. This tag cloud won't
explicitly exist on the org side. Rather it will be implicitly produced
and updated by some (Python) code that runs as part of the JSON->HTML
stage of the exporter.
Cheers,
-Brett.
[-- Attachment #2: Type: application/pgp-signature, Size: 180 bytes --]
next prev parent reply other threads:[~2014-07-23 19:53 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-07-22 23:52 Possible to use src block to generate org headlines for export? Matt Lundin
2014-07-23 1:27 ` Nick Dokos
2014-07-23 2:35 ` Matt Lundin
2014-07-23 2:46 ` Matt Lundin
2014-07-23 13:42 ` Brett Viren
2014-07-23 15:17 ` Matt Lundin
2014-07-23 16:06 ` Charles Berry
2014-07-23 17:07 ` Matt Lundin
2014-07-24 1:51 ` Nick Dokos
2014-07-24 10:21 ` Andreas Leha
2014-07-25 8:31 ` Nicolas Goaziou
2014-07-25 13:05 ` Andreas Leha
2014-07-25 13:23 ` Nicolas Goaziou
2014-07-25 13:39 ` Andreas Leha
2014-07-25 14:26 ` Thorsten Jolitz
2014-07-25 16:08 ` Nicolas Goaziou
2014-07-26 0:26 ` Andreas Leha
2014-07-26 8:07 ` Nicolas Goaziou
2014-07-26 19:47 ` Andreas Leha
2014-07-24 18:40 ` Charles Berry
2014-07-24 19:41 ` Nick Dokos
2014-07-23 19:53 ` Brett Viren [this message]
2014-07-23 20:42 ` Matt Lundin
2014-07-24 22:05 ` Brett Viren
2014-07-23 16:09 ` Rick Frankel
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=ir4r41bsvgt.fsf@lycastus.phy.bnl.gov \
--to=bv@bnl.gov \
--cc=emacs-orgmode@gnu.org \
--cc=mdl@imapmail.org \
--cc=ndokos@gmail.com \
/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).