#+include doesn't export anything?

#+include doesn't export anything?

[James Harkins]

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"
~~

Re: #+include doesn't export anything?

[Nicolas Goaziou]

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

Re: #+include doesn't export anything?

[James Harkins]

On Monday, January 27, 2014 12:36:22 AM HKT, Nicolas Goaziou wrote:
> What happens if you call (org-export-expand-include-keyword) in that
> buffer? Are the resulting changes valid?

(Aside: This was challenging at first, b/c 
org-export-expand-include-keyword is not interactive.)

Ah... now I see it.

#+INCLUDE: "../slidehead.org"
#+include: "../glossary.org"

#+include: "./01-contents.org"

The last heading in glossary.org is ":noexport:" -- then, the include for 
01-contents.org thinks that it should go underneath the last heading to be 
created in glossary.org. So, everything that was a top level heading in 
01-contents.org becomes a second-level heading, underneath a :noexport: 
tag.

So, that pretty much blows my file structure to smithereens.

I suppose it's actually debatable. But, I would have assumed that the last 
heading level in an included file would be "unwound" before including the 
next file. That is:

~~
#+include "something.org"
* Heading
#+include "something-else.org"
~~

... would denote everything in something-else.org by one level, while...

~~
#+include "something.org"

#+include "something-else.org"
~~

... would leave something-else.org's levels untouched, regardless of the 
headline levels in something.org.

Hm. It looks like my whole idea about structuring this project was badly 
conceived from the beginning :(  either that, or the include mechanism is 
not thoroughly thought-through.

hjh

Re: #+include doesn't export anything?

[Nicolas Goaziou]

James Harkins <jamshark70@gmail.com> writes:

> I suppose it's actually debatable. But, I would have assumed that the last 
> heading level in an included file would be "unwound" before including the 
> next file. That is:
>
> ~~
> #+include "something.org"
> * Heading
> #+include "something-else.org"
> ~~
>
> ... would denote everything in something-else.org by one level, while...
>
> ~~
> #+include "something.org"
>
> #+include "something-else.org"
> ~~
>
> ... would leave something-else.org's levels untouched, regardless of the 
> headline levels in something.org.
>
> Hm. It looks like my whole idea about structuring this project was badly 
> conceived from the beginning :(  either that, or the include mechanism is 
> not thoroughly thought-through.

See (info "(org) Include files"), in particular :minlevel keyword.


Regards,

-- 
Nicolas Goaziou

Re: #+include doesn't export anything?

[James Harkins]

[-- Attachment #1: Type: text/plain, Size: 465 bytes --]

On Jan 27, 2014 12:52 AM, "Nicolas Goaziou" <n.goaziou@gmail.com> wrote:
> See (info "(org) Include files"), in particular :minlevel keyword.

Oh... RTFM *sheepish grin*

Workflow for using org:

1. Ask/complain about something on the mailing list.

2. Get a reference to the manual.

3. Find out that org already does that.

Sorry for the complaining tone... I was inches away from declaring Day 1 of
the workshop finished, then ran into this.

Thanks again!

hjh

[-- Attachment #2: Type: text/html, Size: 684 bytes --]