From: John Kitchin <jkitchin@andrew.cmu.edu>
To: Eric Abrahamsen <eric@ericabrahamsen.net>
Cc: emacs-orgmode@gnu.org
Subject: Re: templating with Org?
Date: Mon, 10 Aug 2015 08:01:44 -0400 [thread overview]
Message-ID: <m2mvxzs66v.fsf@andrew.cmu.edu> (raw)
In-Reply-To: <871tfbzo96.fsf@ericabrahamsen.net>
In reviewing these, I discovered I reinvented (and probably not as
well!) the function s-format from s.el
(https://github.com/magnars/s.el). It might be another option for you.
Eric Abrahamsen writes:
> John Kitchin <jkitchin@andrew.cmu.edu> writes:
>
>> I don't have the impression you would need to hijack the export
>> process. It seems like you would need to call a function that gets
>> data from some source (e.g the org document) and then populates a
>> template with that data, and once that is done, call a regular export
>> function. There are a number of template solutions:
>> http://www.emacswiki.org/emacs/CategoryTemplates. I am not sure these
>> are too easy to adapt to what you describe.
>
> That's an interesting idea: going from the base Org file to a massaged
> Org buffer, and then exporting that. I'll try that out for a bit. Thanks
> for that, and for the links!
>
>> I played around with some ideas for this here:
>>
>> http://kitchingroup.cheme.cmu.edu/blog/2014/01/20/Alternatives-to-long-complex-format-statements-in-emacs-lisp/
>>
>> http://kitchingroup.cheme.cmu.edu/blog/2014/01/26/Another-alternative-to-string-templates/
>>
>>
>> Something like these could be used to populate a template I think.
>>
>> John
>>
>> -----------------------------------
>> Professor John Kitchin
>> Doherty Hall A207F
>> Department of Chemical Engineering
>> Carnegie Mellon University
>> Pittsburgh, PA 15213
>> 412-268-7803
>> @johnkitchin
>> http://kitchingroup.cheme.cmu.edu
>>
>> On Sat, Aug 8, 2015 at 12:48 AM, Eric Abrahamsen
>> <eric@ericabrahamsen.net> wrote:
>>
>>
>> Exporting org files and subtrees is awfully flexible, given all
>> the
>> possible customizations, but for a long while I've occasionally
>> felt the
>> need to come at the "export" process from the other direction:
>> instead
>> of customizing the export appearance of a series of headings,
>> instead
>> starting with a common block of export text, and interpolating
>> values
>> from the headings into that text -- ie, templating.
>>
>> I've felt this need off and on for a couple of years, most
>> recently when
>> organizing a small literary festival. I really need to keep all
>> the
>> information about the events in a single place, otherwise I know
>> that
>> information will go stale right away. But I need the information
>> in a
>> series of such wildly-varying formats that I can't imagine setting
>> up
>> (and switching between) export filters in a way that wouldn't make
>> me
>> cry. Not to mention that the different "export" use-cases all have
>> their
>> own per-heading boilerplate text, and there's no way I'm going to
>> repeat
>> all that different boilerplate under each heading.
>>
>> Obviously there's many ways this could be done. I could somehow
>> hijack
>> the export process -- in many cases it would be nice too make use
>> of the
>> skeleton document structures that export provides.
>>
>> Or maybe dynamic blocks? I've never used them before. Or maybe
>> just a
>> plain old `org-map-entries', which reads the template text from an
>> external file and then steals some of the macro expansion
>> functions to
>> fill out the values.
>>
>> Has anyone wanted to do this before? Has anyone actually done it?
>> Any
>> thoughts or suggestions would be much appreciated!
>>
>> Yours,
>> Eric
--
Professor John Kitchin
Doherty Hall A207F
Department of Chemical Engineering
Carnegie Mellon University
Pittsburgh, PA 15213
412-268-7803
@johnkitchin
http://kitchingroup.cheme.cmu.edu
next prev parent reply other threads:[~2015-08-10 12:01 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-08-08 4:48 templating with Org? Eric Abrahamsen
2015-08-08 18:11 ` John Kitchin
2015-08-10 5:49 ` Eric Abrahamsen
2015-08-10 12:01 ` John Kitchin [this message]
2015-08-10 12:14 ` Rasmus
2015-08-10 12:19 ` John Kitchin
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=m2mvxzs66v.fsf@andrew.cmu.edu \
--to=jkitchin@andrew.cmu.edu \
--cc=emacs-orgmode@gnu.org \
--cc=eric@ericabrahamsen.net \
/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).