all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Nicolas Goaziou <mail@nicolasgoaziou.fr>
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 23:47:14 +0100	[thread overview]
Message-ID: <87k2m94kct.fsf@nicolasgoaziou.fr> (raw)
In-Reply-To: <CAFyQvY3gwULTG6wJQC8yrSucYsTiZyC3oYLqB_2CnXpAYbok9g@mail.gmail.com> (Kaushal Modi's message of "Fri, 12 Feb 2016 15:11:23 -0500")

Hello,

Kaushal Modi <kaushal.modi@gmail.com> writes:

> Actually, I just realized that changing those 2 lines to:
>
> #+LaTeX_HEADER: \BeforeBeginEnvironment{minted}{\begin{mdframed}}
> #+LaTeX_HEADER: \AfterEndEnvironment{minted}{\end{mdframed}}
>
> 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?

SETUPFILE exports keywords defined in `org-export-options-alist' and in
back-end specific options (i.e. :options-alist). For example, in latex
back-end the latter category is

  LATEX_CLASS, LATEX_CLASS_OPTIONS, LATEX_HEADER, LATEX_HEADER_EXTRA,
  DESCRIPTION, KEYWORDS, SUBTITLE, LATEX_COMPILER, DATE

Regards,

-- 
Nicolas Goaziou

  parent reply	other threads:[~2016-02-12 22:45 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
2016-02-12 22:47   ` Nicolas Goaziou [this message]
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

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=87k2m94kct.fsf@nicolasgoaziou.fr \
    --to=mail@nicolasgoaziou.fr \
    --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 external index

	https://git.savannah.gnu.org/cgit/emacs.git
	https://git.savannah.gnu.org/cgit/emacs/org-mode.git

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.