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

From: Nicolas Goaziou <n.goaziou@gmail.com>
To: James Harkins <jamshark70@gmail.com>
Cc: orgmode <emacs-orgmode@gnu.org>
Subject: Re: #+include doesn't export anything?
Date: Sun, 26 Jan 2014 17:36:22 +0100	[thread overview]
Message-ID: <87vbx6ya2h.fsf@gmail.com> (raw)
In-Reply-To: <fa864d12-989b-45bb-b874-a719b8b5e594@dewdrop-world.net> (James Harkins's message of "Mon, 27 Jan 2014 00:24:40 +0800")

Hello,

James Harkins <jamshark70@gmail.com> writes:

> I had just asked a question about src-blocks in exports, but things just 
> got a little weirder.
>
> Below is my export file, referring to the master source for day 1. It 
> exports *nothing* from 01-contents.org. I get all the stuff from the 
> header, but 01-contents.org may as well not be there.
>
> Is this a wrong approach?
>
> What's strange is that babel asks me if I want to execute #+call lines that 
> are only in 01-contents.org, but ox-beamer ignores the lot.
>
> ??
>
> I'll find some workaround, but this is highly inconvenient.
>
> hjh
>
>
> ~~
> #+startup: beamer
>
> #+TITLE: SuperCollider Week, Day 1 \\ Introductory SC, Synthesis and 
> Sequencing
> #+DATE: \today
> #+AUTHOR: H. James Harkins
> #+EMAIL:
>
> #+INCLUDE: "../slidehead.org"
> #+include: "../glossary.org"
> #+include: "./01-contents.org"
> ~~

What happens if you call (org-export-expand-include-keyword) in that
buffer? Are the resulting changes valid?


Regards,

-- 
Nicolas Goaziou

next prev parent reply	other threads:[~2014-01-26 16:36 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-01-26 16:24 #+include doesn't export anything? James Harkins
2014-01-26 16:36 ` Nicolas Goaziou [this message]
2014-01-26 16:49   ` James Harkins
2014-01-26 16:52     ` Nicolas Goaziou
2014-01-27  0:58       ` James Harkins

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