emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: James Harkins <jamshark70@gmail.com>
To: Nicolas Goaziou <n.goaziou@gmail.com>
Cc: orgmode <emacs-orgmode@gnu.org>
Subject: Re: #+include doesn't export anything?
Date: Mon, 27 Jan 2014 00:49:32 +0800	[thread overview]
Message-ID: <e3deeb4b-dbfa-44d9-88c0-9afc77767c89@dewdrop-world.net> (raw)
In-Reply-To: <87vbx6ya2h.fsf@gmail.com>

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

  reply	other threads:[~2014-01-26 16:49 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
2014-01-26 16:49   ` James Harkins [this message]
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=e3deeb4b-dbfa-44d9-88c0-9afc77767c89@dewdrop-world.net \
    --to=jamshark70@gmail.com \
    --cc=emacs-orgmode@gnu.org \
    --cc=n.goaziou@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
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).