From: Scott Randby <srandby@gmail.com>
To: Richard Stanton <rhstanton@berkeley.edu>, emacs-orgmode@gnu.org
Subject: Re: How to export a single subtree but include document preamble?
Date: Thu, 4 Apr 2024 14:42:36 -0400 [thread overview]
Message-ID: <d9c2082a-e254-4308-9b9f-56fcc08d3fa9@gmail.com> (raw)
In-Reply-To: <8A1DD68F-1F73-458A-B4AB-4479BDA76882@berkeley.edu>
> On 4/4/24 14:11, Richard Stanton wrote:
> Thanks for the suggestion!
>
> It would still be nice (i.e., you wouldn’t have to do this for every section you ever want to export) to have a way of specifying a line that gets executed for EVERY (say) LaTeX export. Or else an option to do something like include everything in the file before the first section header.
>
>
That would be a nice feature, but I also like using the 'PROPERTIES' drawer because it enables me to have very fine control over the export of a subtree. A typical drawer I use looks like this:
:PROPERTIES:
:EXPORT_TITLE: *Subtree Title*
:EXPORT_FILE_NAME: Exported-Subtree
:EXPORT_LATEX_HEADER_EXTRA: \input{latex-preamble.tex} \hypersetup{pdftitle={Subtree Title},pdfauthor={Scott Randby},pdfsubject={},pdfkeywords={},pdfproducer={Emacs Org},pdfcreator={pdflatex}} \hypersetup{colorlinks=true,urlcolor=blue,linkcolor=blue} %\pagestyle{empty} % Turn page numbering off
:EXPORT_OPTIONS: h:4 author:nil email:nil date:nil creator:nil timestamp:nil tags:nil num:0 toc:nil
:END:
Scott
next prev parent reply other threads:[~2024-04-04 18:43 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-04-04 18:11 How to export a single subtree but include document preamble? Richard Stanton
2024-04-04 18:32 ` Richard Stanton
2024-04-04 18:42 ` Scott Randby [this message]
-- strict thread matches above, loose matches on Subject: below --
2024-04-03 19:00 Richard H. Stanton
2024-04-03 21:13 ` Scott Randby
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=d9c2082a-e254-4308-9b9f-56fcc08d3fa9@gmail.com \
--to=srandby@gmail.com \
--cc=emacs-orgmode@gnu.org \
--cc=rhstanton@berkeley.edu \
/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).