On Jan 27, 2014 12:52 AM, "Nicolas Goaziou" 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 t
James Harkins 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
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
Hello,
James Harkins 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-con
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 t
