From: Mike Gauland <firstname.lastname@example.org>
Subject: LaTeX Headers not in partial export
Date: Fri, 23 Oct 2020 15:22:11 +1300 [thread overview]
Message-ID: <email@example.com> (raw)
Not sure if I'm doing something wrong, or this is expected.
I have a number of #+LATEX directives at the top of my org file, for
configuring the minted package.
When I export the whole thing to LaTeX, the source blocks are formatted
with the desired minted options.
If I export only part of the document--either my marking it, or by
adding an "export" tag--the source blocks are *not* formatted with the
desired options. On looking at the generated tex file, I find that the
options from the top of the org file are missing.
Does this sound like a bug, or user (possibly local configuration)
error? If the former, I'll generate a small file that demonstrates the
next reply other threads:[~2020-10-23 2:23 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-10-23 2:22 Mike Gauland [this message]
2020-10-23 15:00 ` LaTeX Headers not in partial export Eric S Fraga
2020-10-25 2:38 ` Michael Gauland
2020-10-25 2:45 ` Kyle Meyer
2020-10-25 3:00 ` Michael Gauland
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).