From mboxrd@z Thu Jan 1 00:00:00 1970 From: Brett Viren Subject: Re: Possible to use src block to generate org headlines for export? Date: Wed, 23 Jul 2014 15:53:22 -0400 Message-ID: References: <87zjg1gddd.fsf@fastmail.fm> <87wqb4amqb.fsf@gmail.com> <8738dshkdw.fsf@fastmail.fm> <8761io2jnz.fsf@fastmail.fm> Mime-Version: 1.0 Content-Type: multipart/signed; boundary="=-=-="; micalg=pgp-sha1; protocol="application/pgp-signature" Return-path: Received: from eggs.gnu.org ([2001:4830:134:3::10]:42492) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1XA2bm-00036z-7S for emacs-orgmode@gnu.org; Wed, 23 Jul 2014 15:53:55 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1XA2bh-0002U9-89 for emacs-orgmode@gnu.org; Wed, 23 Jul 2014 15:53:50 -0400 Received: from smtpgw.bnl.gov ([2620:10a:0:3::30]:9720 helo=iron3.sec.bnl.local) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1XA2bh-0002Rk-3k for emacs-orgmode@gnu.org; Wed, 23 Jul 2014 15:53:45 -0400 In-Reply-To: <8761io2jnz.fsf@fastmail.fm> (Matt Lundin's message of "Wed, 23 Jul 2014 10:17:36 -0500") List-Id: "General discussions about Org-mode." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: emacs-orgmode-bounces+geo-emacs-orgmode=m.gmane.org@gnu.org Sender: emacs-orgmode-bounces+geo-emacs-orgmode=m.gmane.org@gnu.org To: Matt Lundin Cc: Nick Dokos , emacs-orgmode@gnu.org --=-=-= Content-Type: text/plain Content-Transfer-Encoding: quoted-printable Matt Lundin writes: > Brett Viren writes: >> >> Maybe it would be more convenient to add the "meta-ness" you want as >> part of a new exporter process?=20=20 > > To change the "meta" wrappers for code block results, we would have to > modify org babel (ob-core.el).=20 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, =2DBrett. --=-=-= Content-Type: application/pgp-signature -----BEGIN PGP SIGNATURE----- Version: GnuPG v1 iEYEARECAAYFAlPQErIACgkQEixH2Z0dKCwxDwCfYAxh9o1aGZkEpF2aVzIp01O7 3cMAniHXWVYo8a3zNRloHVKxps03gEsK =uHG4 -----END PGP SIGNATURE----- --=-=-=--