From: Eric S Fraga <e.fraga@ucl.ac.uk>
To: Emacs Org mode mailing list <emacs-orgmode@gnu.org>
Subject: Something to watch out for when including files
Date: Tue, 20 Sep 2016 16:21:19 +0100 [thread overview]
Message-ID: <87y42mfvgw.fsf@ucl.ac.uk> (raw)
Hello all,
just wanted to help others avoid spending a long time trying to figure
out some strange (well, unexpected) behaviour in org...
I have a document for which the LaTeX export was ignoring a
#+begin_abstract ... #+end_abstract construct near the start of the
document. The text was simply not appearing in the LaTeX file.
Long story short: 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.
Took me a very long time to figure out... the simple solution was to
remove that noexport section entirely from the preamble file.
I do wonder whether the org export approach (i.e. how it "includes"
files) is correct but I can understand why the implementation is the way
it is.
Thanks for listening!
eric
--
: Eric S Fraga (0xFFFCF67D), Emacs 25.1.50.1, Org release_8.3.6-1149-g582233
next reply other threads:[~2016-09-20 16:53 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-09-20 15:21 Eric S Fraga [this message]
2016-09-20 17:10 ` Something to watch out for when including files 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
[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=87y42mfvgw.fsf@ucl.ac.uk \
--to=e.fraga@ucl.ac.uk \
--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.