From: Carsten Dominik <carsten.dominik@gmail.com>
To: Dan Davison <davison@stats.ox.ac.uk>
Cc: emacs org-mode mailing list <emacs-orgmode@gnu.org>
Subject: Re: #+include: export header lines
Date: Tue, 14 Apr 2009 13:21:43 +0200 [thread overview]
Message-ID: <44EF98DA-99F1-4DFE-BAEF-55B46A363574@gmail.com> (raw)
In-Reply-To: <87d4bgtl0s.fsf@stats.ox.ac.uk>
Hi Dan,
special lines like #+OPTIONS are only parsed if the file is
pointed to with
#+SETUPFILE: "~/src/common/org-header.org"
HTH
- Carsten
P.S. Where should we have had what documentation
to make this easier for you to find?
On Apr 13, 2009, at 9:24 PM, Dan Davison wrote:
> Dear list,
>
> I'm failing to work out how to #+include: a file containing export
> header directives in such a way that the directives are obeyed.
>
> I tried creating this file tmp.org
>
> ----------------------------------------------------------------
> #+include: "~/src/common/org-header.org"
> * heading 1
> ----------------------------------------------------------------
>
> where the contents of org-header.org are
>
> ----------------------------------------------------------------
> #+OPTIONS: H:3 num:nil toc:t \n:nil @:t ::t |:t ^:{} -:t f:t *:t
> TeX:t LaTeX:t skip:nil d:(HIDE) tags:not-in-toc
> #+STYLE: <link rel="stylesheet" type="text/css" href="/home/dan/src/
> common/dan.css" />
> #+AUTHOR: Dan Davison
> #+EMAIL: davison@stats.ox.ac.uk
>
> * this is org-header; that_1 shouldn't be a subscript
> ----------------------------------------------------------------
>
> On export of tmp.org I *do* get the heading from org-header.org, but I
> do not get the effects of the export directives in org-header.org
> (dan.css didn't happen, and the _1 subscript comes out as a
> subscript). In contrast when I export org-header.org itself, I do of
> course get the effects of the export options.
>
> I am conscious that most if not all of my previous posts of this
> nature
> have resulted in me being pointed to the section of the manual I
> *should* have been familiar with! So, for the record, for this
> problem I
> looked at
>
> http://orgmode.org/manual/Export-options.html#Export-options
> http://orgmode.org/manual/Include-files.html#index-g_t_0023_002bINCLUDE-878
>
> OTOH I just grepped through the contents of Worg and found no such
> mechanism being used, so perhaps I am for once asking for something
> that
> doesn't already exist.
>
> Thanks a lot,
>
> Dan
>
>
> _______________________________________________
> Emacs-orgmode mailing list
> Remember: use `Reply All' to send replies to the list.
> Emacs-orgmode@gnu.org
> http://lists.gnu.org/mailman/listinfo/emacs-orgmode
next prev parent reply other threads:[~2009-04-14 11:21 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-04-13 19:24 #+include: export header lines Dan Davison
2009-04-14 11:21 ` Carsten Dominik [this message]
2009-04-14 16:35 ` Dan Davison
2009-04-15 6:43 ` Carsten Dominik
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=44EF98DA-99F1-4DFE-BAEF-55B46A363574@gmail.com \
--to=carsten.dominik@gmail.com \
--cc=davison@stats.ox.ac.uk \
--cc=emacs-orgmode@gnu.org \
/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
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
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).