John Hendy <jw.he...@gmail.com> wrote: > I use beamer a lot for work and decided to create a beamer-specific > setupfile to clean up my org files a bit. My files typically contain a > header like so: > > --- > #+latex_class: beamer > #+startup: beamer > #+options: toc:nil latex:t tex:t > #+latex_class_options: [presentation,bigger] > #+beamer_frame_level: 1 > #+beamer_header_extra: > \usetheme[alternativetitlepage=true,titleline=true,titlepagelogo=../pics/pic.jpg]{Torino} > #+beamer_header_extra: \usecolortheme{freewilly} > > #+latex_header: \usepackage{tikz} > #+latex_header: > \usetikzlibrary{decorations,arrows,automata,positioning,backgrounds} > > #+latex_header: \usepackage{setspace} > #+latex_header: \setstretch{1.3} > > #+latex_header: \usepackage{lmodern} > #+latex_header: \usepackage{booktabs} > #+AUTHOR: John Henderson > --- > > I tried inserting the above into a file called =beamer-setup.org= and > simply doing: > --- > #+setupfile: ~/org/aux/beamer-setup.org > --- > > This doesn't seem to work, however. My theme doesn't get picked up, > for example. If I put the contents into the file directly, I'm all > set. Any suggestions on why this might be the case? >
C-c C-c on the setupfile line? The doc says ,---- | `#+SETUPFILE: file' | This line defines a file that holds more in-buffer setup. | Normally this is entirely ignored. Only when the buffer is parsed | for option-setting lines (i.e. when starting Org mode for a file, | when pressing `C-c C-c' in a settings line, or when exporting), | then the contents of this file are parsed as if they had been | included in the buffer. In particular, the file can be any other | Org mode file with internal setup. You can visit the file the | cursor is in the line with `C-c ''. `---- and when I try the export, it fails to find "freewilly.sty" (no surprise there), which seems to show that the file *is* processed. Nick