emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Nicolas Goaziou <n.goaziou@gmail.com>
To: John Hendy <jw.hendy@gmail.com>
Cc: emacs-orgmode <emacs-orgmode@gnu.org>
Subject: Re: Including setupfile settings during subtree export (new exporter)
Date: Fri, 22 Mar 2013 16:27:03 +0100	[thread overview]
Message-ID: <87obebwj3s.fsf@gmail.com> (raw)
In-Reply-To: <CA+M2ft9GHqe+fh6J3bCyRc5=-dRPLFZTa19sKzto25xBx+9atA@mail.gmail.com> (John Hendy's message of "Fri, 22 Mar 2013 10:19:33 -0500")


John Hendy <jw.hendy@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:
> "/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 =#+include: "file"= as well as =#+setupfile: file=
> inside the subtree properties drawer without success.

Inside the property drawer? A property drawer can only contain node
properties, e.g.:

  :PROP: value

> If I mark the same subtree with :export: tag (no other trees are
> marked), it works properly and uses my setupfile options.
> Any suggestions? If this was an oversight, my vote would be that a
> buffer-set setupfile would apply to subtree exports unless overridden
> by a property-drawer setting (even though I don't currently know that
> the property draw setting is for a setupfile).

I think I need an ECM to understand the problem you're describing.


Nicolas Goaziou

  reply	other threads:[~2013-03-22 15:27 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 [this message]
2013-03-22 17:12   ` John Hendy
2013-03-23 20:24     ` Nicolas Goaziou
2013-03-23 20:37       ` John Hendy
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:

  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=87obebwj3s.fsf@gmail.com \
    --to=n.goaziou@gmail.com \
    --cc=emacs-orgmode@gnu.org \
    --cc=jw.hendy@gmail.com \


* 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 public inbox


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