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 12:51:15 +0000 [thread overview]
Message-ID: <8760w9tnb0.fsf@ucl.ac.uk> (raw)
In-Reply-To: <56F677E8.3050009@verizon.net> (Charles Millar's message of "Sat, 26 Mar 2016 07:52:08 -0400")
On Saturday, 26 Mar 2016 at 07:52, Charles Millar wrote:
[...]
> Thanks for the correction. I escaped the \foo otherwise I had a
> spurious "oobar" at the beginning of the exported document so that my
> latex class has
>
> \newcommand{\\foo}{bar}
>
> I suspect that this problem may be file specific. I exported another
> file, using the same SETUPFILE and had no problems
It may have "worked" but the odds are that you were simply
lucky. \newcommand expects two {} arguments, the first being the name
of the command and the second the actual sequence to execute.
--
: 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 13:06 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 [this message]
2016-03-26 14:15 ` Charles Millar
2016-03-26 17:14 ` Eric S Fraga
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=8760w9tnb0.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).