all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Giacomo M <jackjackk@gmail.com>
To: emacs-orgmode@gnu.org
Subject: Re: Something to watch out for when including files
Date: Wed, 21 Sep 2016 17:22:00 +0200	[thread overview]
Message-ID: <79b09cc4-7263-06d4-babd-7352f638ec10@gmail.com> (raw)
In-Reply-To: <87y42mfvgw.fsf@ucl.ac.uk>


Il 20/09/2016 17:21, Eric S Fraga ha scritto:
> I had a #+include: directive as the first line of the
> file which included an org file called preamble.org.  In that preamble
> file, the last headline had the tag :noexport:.  It would seem that this
> tag is not processed until after the include file has been included.  I
> hope that makes sense.  In any case, this means that my abstract was
> considered to be part of the noexport headline and was therefore not
> exported.

Lately I like to have headlines for all the logical parts of the 
document, so also an "Abstract" headline with the abstract block inside. 
Then I use the tag "ignore" and the org export extra "ignore-headlines" 
(activated e.g. via "(ox-extras-activate '(ignore-headlines))" if you 
use org-plus-contrib) to avoid exporting the headlines themselves. This 
should also avoid the inheritance of tags in the last headline of the 
include. Not vanilla org, but I find it handy.

Giacomo

  parent reply	other threads:[~2016-09-21 15:23 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-09-20 15:21 Something to watch out for when including files Eric S Fraga
2016-09-20 17:10 ` Adam Porter
2016-09-20 23:32 ` Charles C. Berry
     [not found] ` <58a8c0419a56444fb6956cd709d26dec@HE1PR01MB1898.eurprd01.prod.exchangelabs.com>
2016-09-21  6:44   ` Eric S Fraga
2016-09-21 15:22 ` Giacomo M [this message]
     [not found] ` <b81ae1e313fc4a0c85fa5d63e3c29eb2@HE1PR01MB1898.eurprd01.prod.exchangelabs.com>
2016-09-21 15:53   ` Eric S Fraga

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

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=79b09cc4-7263-06d4-babd-7352f638ec10@gmail.com \
    --to=jackjackk@gmail.com \
    --cc=emacs-orgmode@gnu.org \
    /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 external index

	https://git.savannah.gnu.org/cgit/emacs.git
	https://git.savannah.gnu.org/cgit/emacs/org-mode.git

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.