* #+include doesn't export anything?
@ 2014-01-26 16:24 James Harkins
2014-01-26 16:36 ` Nicolas Goaziou
0 siblings, 1 reply; 5+ messages in thread
From: James Harkins @ 2014-01-26 16:24 UTC (permalink / raw)
To: orgmode
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"
~~
^ permalink raw reply [flat|nested] 5+ messages in thread
* Re: #+include doesn't export anything?
2014-01-26 16:24 #+include doesn't export anything? James Harkins
@ 2014-01-26 16:36 ` Nicolas Goaziou
2014-01-26 16:49 ` James Harkins
0 siblings, 1 reply; 5+ messages in thread
From: Nicolas Goaziou @ 2014-01-26 16:36 UTC (permalink / raw)
To: James Harkins; +Cc: orgmode
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
^ permalink raw reply [flat|nested] 5+ messages in thread
* Re: #+include doesn't export anything?
2014-01-26 16:36 ` Nicolas Goaziou
@ 2014-01-26 16:49 ` James Harkins
2014-01-26 16:52 ` Nicolas Goaziou
0 siblings, 1 reply; 5+ messages in thread
From: James Harkins @ 2014-01-26 16:49 UTC (permalink / raw)
To: Nicolas Goaziou; +Cc: orgmode
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
^ permalink raw reply [flat|nested] 5+ messages in thread
* Re: #+include doesn't export anything?
2014-01-26 16:49 ` James Harkins
@ 2014-01-26 16:52 ` Nicolas Goaziou
2014-01-27 0:58 ` James Harkins
0 siblings, 1 reply; 5+ messages in thread
From: Nicolas Goaziou @ 2014-01-26 16:52 UTC (permalink / raw)
To: James Harkins; +Cc: orgmode
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
^ permalink raw reply [flat|nested] 5+ messages in thread
end of thread, other threads:[~2014-01-27 0:59 UTC | newest]
Thread overview: 5+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2014-01-26 16:24 #+include doesn't export anything? James Harkins
2014-01-26 16:36 ` Nicolas Goaziou
2014-01-26 16:49 ` James Harkins
2014-01-26 16:52 ` Nicolas Goaziou
2014-01-27 0:58 ` James Harkins
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).