[O] Help understanding what's imported from a #+SETUPFILE file

Hi, I have a common setup file for all my org files which configure the way the latex and HTML files are exported. #+SETUPFILE: ~/org/common/config.org One of the snippets in my config.org is # Allow multi-page code listings by wrapping the `minted' environment with `mdframed' environment #

Re: [O] Help understanding what's imported from a #+SETUPFILE file

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

Re: [O] Help understanding what's imported from a #+SETUPFILE file

Hello, Kaushal Modi 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

Re: [O] Help understanding what's imported from a #+SETUPFILE file

> SETUPFILE exports keywords defined in `org-export-options-alist' and in > back-end specific options (i.e. :options-alist). I tried "C-h v org-export-options-alist" but the result seemed cryptic to me: ((:title "TITLE" nil nil parse) (:date "DATE" nil nil parse) (:author "AUTHOR" nil

Re: [O] Help understanding what's imported from a #+SETUPFILE file

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

Re: [O] Help understanding what's imported from a #+SETUPFILE file

Hello, Kaushal Modi writes: >> SETUPFILE exports keywords defined in `org-export-options-alist' and in >> back-end > specific options (i.e. :options-alist). > > I tried "C-h v org-export-options-alist" but the result seemed cryptic to > me: Quoting its docstring: