From: John Kitchin <firstname.lastname@example.org>
To: Matt Price <email@example.com>
Cc: Org Mode <firstname.lastname@example.org>
Subject: Re: add a heading w/ #+print_bibliography to parse tree on export
Date: Fri, 30 Jul 2021 21:01:36 -0400 [thread overview]
Message-ID: <CAJ51ETrs7c7TLE_jiri=hdiyqQ=Yywoc_iZkTtO0Z97v0jXxMA@mail.gmail.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 2230 bytes --]
I think the way to do this is to use a function in
org-export-before-processing-hook to add it if you don't find it.
you can still use org-ml to generate the string that gets inserted. I guess
you would just go to the end of the buffer and insert it.
Professor John Kitchin (he/him/his)
Doherty Hall A207F
Department of Chemical Engineering
Carnegie Mellon University
Pittsburgh, PA 15213
On Fri, Jul 30, 2021 at 8:18 PM Matt Price <email@example.com> wrote:
> conditionally add a headline with content to parse tree using either
> org-export-before-parsing-hook or org-export-filter-parse-tree-functions
> I use org-re-reveal to make lecture slides from subtrees. Often I forget
> to add a heading with #+print_bibliography: and as a result org-cite does
> not generate the bibliography, and my citations are not wrapped in links.
> I'd like to search *either* the parse tree *or* the temporary export
> buffer for the #+print_bibliography keyword, and if it's not found, add a
> headline to the end of the subtree/parse-tree with the appropriate
> I can easily generate the proper lisp object with the org-ml package:
> (org-ml-build-headline :title '("Sources")
> (org-ml-build-node-property "CUSTOM_ID"
> (org-ml-build-keyword "print_bibliography" "" )
> And if I want I can turn that into a string by wrapping it in
> (org-ml-to-trimmed-string ...)
> However, I'm not sure how best to add it to the exported data. I believe
> I can add a function to either org-export-before-parsing-hook or
> org-export-filter-parse-tree-functions, but beyond that I'm a bit lost.
> It's not immediately obvious how to find the last headline and append
> another headline after that headline's section. Looking at the nesting
> confuses me somewhat and I'm afraid I'll break the data structure.
> Has anyone done something like this before and do you have ideas?
> Thank you!
[-- Attachment #2: Type: text/html, Size: 3180 bytes --]
next prev parent reply other threads:[~2021-07-31 1:02 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-07-31 0:17 add a heading w/ #+print_bibliography to parse tree on export Matt Price
2021-07-31 1:01 ` John Kitchin [this message]
2021-08-01 0:05 ` Matt Price
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:
List information: https://www.orgmode.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
* 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
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).