emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed

From: John Hendy <jw.hendy@gmail.com>
To: Nicolas Goaziou <n.goaziou@gmail.com>
Cc: emacs-orgmode <emacs-orgmode@gnu.org>
Subject: Re: Including setupfile settings during subtree export (new exporter)
Date: Sat, 23 Mar 2013 15:37:08 -0500	[thread overview]
Message-ID: <CA+M2ft-8bN-gbN+b78CBv0=WU-TdAda1rukcyOExF-zkKjpR4Q@mail.gmail.com> (raw)
In-Reply-To: <87620h27br.fsf@gmail.com>

On Sat, Mar 23, 2013 at 3:24 PM, Nicolas Goaziou <n.goaziou@gmail.com> wrote:
> Hello,
>
> John Hendy <jw.hendy@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 "#+setupfile:" instead of "#+include:"
>
> There's a major difference between "setupfile" and "include" keyword
> here: the former applies to the whole buffer, whereas the latter is only
> expanded in the part being exported.

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)

#+begin_quote

Other important changes

#+STYLE: -> #+HTML_HEAD:
#+SETUPFILE: myfile -> =#+INCLUDE: "myfile"=

#+end_quote

That reads, to me, as though the syntax changed. Perhaps the "->"
didn't mean what I took it to mean?

>
> In your case, the INCLUDE keyword doesn't belong to the subtree, so it
> is never expanded.

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 override the buffer-wide
setupfile.

Based on the above, should that line be removed from the Worg update
guide? If so, I can do that. If someone has a better understanding of
why it was included (perhaps #+include is a new feature and should be
better explained), then maybe they should do it.

I'll change back to #+setupfile!


Thanks for the assistance,
John



>
> Regards,
>
> --
> Nicolas Goaziou

next prev parent reply	other threads:[~2013-03-23 20:37 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-03-22 15:19 Including setupfile settings during subtree export (new exporter) John Hendy
2013-03-22 15:27 ` Nicolas Goaziou
2013-03-22 17:12   ` John Hendy
2013-03-23 20:24     ` Nicolas Goaziou
2013-03-23 20:37       ` John Hendy [this message]
2013-03-23 20:49         ` Nicolas Goaziou
2013-03-23 21:10           ` John Hendy
2013-03-23 22:08             ` Nicolas Goaziou
2013-03-23 22:18               ` John Hendy
2013-03-23 22:37                 ` Nicolas Goaziou
2013-03-24 12:13         ` Mike McLean

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='CA+M2ft-8bN-gbN+b78CBv0=WU-TdAda1rukcyOExF-zkKjpR4Q@mail.gmail.com' \
    --to=jw.hendy@gmail.com \
    --cc=emacs-orgmode@gnu.org \
    --cc=n.goaziou@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

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).