From mboxrd@z Thu Jan 1 00:00:00 1970 From: James Harkins Subject: Re: #+include doesn't export anything? Date: Mon, 27 Jan 2014 00:49:32 +0800 Message-ID: References: <87vbx6ya2h.fsf@gmail.com> Mime-Version: 1.0 Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: quoted-printable Return-path: Received: from eggs.gnu.org ([2001:4830:134:3::10]:52372) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1W7Su9-00041w-91 for emacs-orgmode@gnu.org; Sun, 26 Jan 2014 11:49:57 -0500 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1W7Su5-00069R-0s for emacs-orgmode@gnu.org; Sun, 26 Jan 2014 11:49:53 -0500 Received: from mail-pa0-x22b.google.com ([2607:f8b0:400e:c03::22b]:41631) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1W7Su4-00069N-Po for emacs-orgmode@gnu.org; Sun, 26 Jan 2014 11:49:48 -0500 Received: by mail-pa0-f43.google.com with SMTP id rd3so5045512pab.2 for ; Sun, 26 Jan 2014 08:49:47 -0800 (PST) In-Reply-To: <87vbx6ya2h.fsf@gmail.com> List-Id: "General discussions about Org-mode." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: emacs-orgmode-bounces+geo-emacs-orgmode=m.gmane.org@gnu.org Sender: emacs-orgmode-bounces+geo-emacs-orgmode=m.gmane.org@gnu.org 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=20 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=20 01-contents.org thinks that it should go underneath the last heading to be=20= created in glossary.org. So, everything that was a top level heading in=20 01-contents.org becomes a second-level heading, underneath a :noexport:=20 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=20= heading level in an included file would be "unwound" before including the=20 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=20 headline levels in something.org. Hm. It looks like my whole idea about structuring this project was badly=20 conceived from the beginning :( either that, or the include mechanism is=20 not thoroughly thought-through. hjh