From: Eric S Fraga <e.fraga@ucl.ac.uk>
To: Kaushal Modi <kaushal.modi@gmail.com>
Cc: emacs-org list <emacs-orgmode@gnu.org>
Subject: Re: Help understanding what's imported from a #+SETUPFILE file
Date: Fri, 12 Feb 2016 20:50:49 +0000 [thread overview]
Message-ID: <87a8n5tzyu.fsf@ucl.ac.uk> (raw)
In-Reply-To: <CAFyQvY3gwULTG6wJQC8yrSucYsTiZyC3oYLqB_2CnXpAYbok9g@mail.gmail.com> (Kaushal Modi's message of "Fri, 12 Feb 2016 15:11:23 -0500")
On Friday, 12 Feb 2016 at 15:11, Kaushal Modi wrote:
> Actually, I just realized that changing those 2 lines to:
>
> #+LaTeX_HEADER: \BeforeBeginEnvironment{minted}{\begin{mdframed}}
> #+LaTeX_HEADER: \AfterEndEnvironment{minted}{\end{mdframed}}
This is indeed the solution.
> in the SETUPFILE works too. I don't recall the reason why I did not have
> them as LaTeX_HEADER earlier.
>
> But the question still remains.. is SETUPFILE designed to not export lines
> beginning with #+LaTeX? Or a general question would be.. what stuff doesn't
> SETUPFILE export?
I think you'll find that anything before the first headline (other than
header lines and document settings) is ignored when exporting to
LaTeX and that applies to all text, whether in the main file or from an
included file.
--
: Eric S Fraga (0xFFFCF67D), Emacs 25.0.90.1, Org release_8.3.3-565-g4f499f
next prev parent reply other threads:[~2016-02-12 20:51 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-02-12 20:02 Help understanding what's imported from a #+SETUPFILE file Kaushal Modi
2016-02-12 20:11 ` Kaushal Modi
2016-02-12 20:50 ` Eric S Fraga [this message]
2016-02-12 22:47 ` Nicolas Goaziou
2016-02-12 23:02 ` Kaushal Modi
2016-02-12 23:35 ` Nicolas Goaziou
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=87a8n5tzyu.fsf@ucl.ac.uk \
--to=e.fraga@ucl.ac.uk \
--cc=emacs-orgmode@gnu.org \
--cc=kaushal.modi@gmail.com \
/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).