From: Eric S Fraga <e.fraga@ucl.ac.uk>
To: Charles Millar <millarc@verizon.net>
Cc: emacs-orgmode@gnu.org
Subject: Re: first #+LATEX_HEADER: in SETUPFILE not correctly exported and causes Missing \begin{document} error
Date: Sat, 26 Mar 2016 17:14:51 +0000 [thread overview]
Message-ID: <87oaa1rwj8.fsf@ucl.ac.uk> (raw)
In-Reply-To: <56F6997B.70505@verizon.net> (Charles Millar's message of "Sat, 26 Mar 2016 10:15:23 -0400")
On Saturday, 26 Mar 2016 at 10:15, Charles Millar wrote:
[...]
> I was not clear - I ran the exports after I made the correction to
> "mysetup", i.e. \newcommand{\\foo}{bar}
but I am confused: why the \\ for foo but \ for newcommand? What is the
actual result in the output.tex file?
> I do agree that the one file that exports as desired must be a result
> of luck. I compared the output.tex file for each document. In each the
> first \usepackage{foo} which is inserted from the SETUPFILE is
> indented several tabs or spaces to the right and not aligned to the
> left margin.
The indentation or not itself is not the issue but only a symptom of an
error before that line, in my opinion.
--
: Eric S Fraga (0xFFFCF67D), Emacs 25.0.92.1, Org release_8.3.4-668-g809a83
next prev parent reply other threads:[~2016-03-26 17:15 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-03-26 0:56 first #+LATEX_HEADER: in SETUPFILE not correctly exported and causes Missing \begin{document} error Charles Millar
2016-03-26 0:58 ` Charles Millar
2016-03-26 9:36 ` Eric S Fraga
2016-03-26 11:52 ` Charles Millar
2016-03-26 12:51 ` Eric S Fraga
2016-03-26 14:15 ` Charles Millar
2016-03-26 17:14 ` Eric S Fraga [this message]
2016-03-26 22:55 ` Charles Millar
2016-03-28 14:54 ` Charles Millar
2016-03-29 10:50 ` Eric S Fraga
2016-04-02 9:00 ` Nicolas Goaziou
2016-04-03 18:18 ` Charles Millar
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=87oaa1rwj8.fsf@ucl.ac.uk \
--to=e.fraga@ucl.ac.uk \
--cc=emacs-orgmode@gnu.org \
--cc=millarc@verizon.net \
/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).