On Sat, Mar 23, 2013 at 4:37 PM, John Hendy jw.he...@gmail.com wrote:
Huh, well that's interesting. I /had/ #+setupfile, and only changed
due to following the upgrade guide
(http://orgmode.org/worg/org-8.0.html)
FWIW, I had read the same thing and made the same #+SETUPFILE → #+INCLUDE
Hello,
John Hendy jw.he...@gmail.com writes:
#+begin_src setupfile
#+AUTHOR:John Henderson
#+latex_header: \usepackage[hmargin=2.5cm,vmargin=2.5cm]{geometry}
#+latex_header: \usepackage{mathpazo}
#+end_src
#+begin_src test-setupfile.org
#+include: /path/to/setupfile
Use
On Sat, Mar 23, 2013 at 3:24 PM, Nicolas Goaziou n.goaz...@gmail.com wrote:
Hello,
John Hendy jw.he...@gmail.com writes:
#+begin_src setupfile
#+AUTHOR:John Henderson
#+latex_header: \usepackage[hmargin=2.5cm,vmargin=2.5cm]{geometry}
#+latex_header: \usepackage{mathpazo}
#+end_src
John Hendy jw.he...@gmail.com writes:
Thanks for the clarification. For me (since I'm not an elisper), the
mechanics aren't too important. All I really want is the correct way
to apply org-mode settings to a buffer or a subtree by default, unless
I specify otherwise inside a subtree to
On Sat, Mar 23, 2013 at 3:49 PM, Nicolas Goaziou n.goaz...@gmail.com wrote:
John Hendy jw.he...@gmail.com writes:
Thanks for the clarification. For me (since I'm not an elisper), the
mechanics aren't too important. All I really want is the correct way
to apply org-mode settings to a buffer or
John Hendy jw.he...@gmail.com writes:
At the moment, there's no way to override a #+setupfile: keyword
locally.
I guess I don't understand the purpose of #+include, then. It seems we
have only two options:
1) #+setupfile: Will apply to entire buffer as well as subtree
exports. Cannot be
On Sat, Mar 23, 2013 at 5:08 PM, Nicolas Goaziou n.goaz...@gmail.com wrote:
John Hendy jw.he...@gmail.com writes:
At the moment, there's no way to override a #+setupfile: keyword
locally.
I guess I don't understand the purpose of #+include, then. It seems we
have only two options:
1)
John Hendy jw.he...@gmail.com writes:
#+INCLUDE: file replaces keyword with file contents. During subtree
export, replacement will happen if the keyword is located within the
subtree being exported.
#+SETUPFILE: file just reads Org keywords within file. All Org
keywords are global, this one
In the past, exporting a subtree seemed to pull options from my
#+setupfile line.
I've updated the line to the proper new syntax (#+include:
/path/to/setupfile.org), but subtree export doesn't seem to be using
the options set there (using =C-c C-e C-s l p= for LaTeX/PDF export).
I tried using
On Fri, Mar 22, 2013 at 10:27 AM, Nicolas Goaziou n.goaz...@gmail.com wrote:
Hello,
John Hendy jw.he...@gmail.com writes:
In the past, exporting a subtree seemed to pull options from my
#+setupfile line.
And it should still do.
I've updated the line to the proper new syntax (#+include:
10 matches
Mail list logo