From: Nicolas Goaziou <mail@nicolasgoaziou.fr>
To: Robert Klein <roklein@roklein.de>
Cc: emacs-orgmode@gnu.org
Subject: Re: org export outcomes differ from one attempt to the next
Date: Mon, 21 Sep 2015 22:25:33 +0200 [thread overview]
Message-ID: <87oagvcyf6.fsf@nicolasgoaziou.fr> (raw)
In-Reply-To: <878u7zzgrp.fsf@ucl.ac.uk> (Eric S. Fraga's message of "Mon, 21 Sep 2015 20:58:18 +0100")
Hello,
Eric S Fraga <e.fraga@ucl.ac.uk> writes:
> Actually, my settings are at the end of the whole 4000+ line file so I
> am not sure what you are suggesting I try. If I delete the whole
> settings subtree, the exports all result in the same LaTeX. However,
> that is of no use to me, obviously. I guess I can try to add one line
> at a time to see when the export breaks. I may try that tomorrow.
Providing a shorter test file would be helpful, no matter how much
settings you have.
> I guess I would like some insight into how the latex_header lines are
> parsed by org, maybe in org-element?
They are collected in `org-export--get-inbuffer-options' which is called
by `org-export-get-environment'.
IIRC, Robert Klein's problem was due to an explicit call to
`org-export-get-environment' at Babel evaluation time, before the buffer
was correctly prepared for export. If you call
`org-export-get-environment' within your settings, it may be related.
Regards,
--
Nicolas Goaziou
next prev parent reply other threads:[~2015-09-21 20:23 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-09-21 15:15 org export outcomes differ from one attempt to the next Eric S Fraga
2015-09-21 15:40 ` Eric S Fraga
2015-09-21 18:21 ` Robert Klein
2015-09-21 19:58 ` Eric S Fraga
2015-09-21 20:25 ` Nicolas Goaziou [this message]
2015-09-29 8:20 ` Robert Klein
2015-09-29 15:52 ` Nicolas Goaziou
2015-10-01 9:28 ` Eric S Fraga
2015-10-01 20:02 ` Nicolas Goaziou
2015-10-02 7:37 ` 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
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=87oagvcyf6.fsf@nicolasgoaziou.fr \
--to=mail@nicolasgoaziou.fr \
--cc=emacs-orgmode@gnu.org \
--cc=roklein@roklein.de \
/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).