From: Carsten Dominik <email@example.com>
To: Russell Adams <RLAdams@AdamsInfoServ.Com>
Cc: emacs org-mode mailing list <firstname.lastname@example.org>
Subject: Re: FR: Define Latex macros from export header
Date: Sat, 21 Feb 2009 14:03:54 +0100 [thread overview]
Message-ID: <D7D55EEC-CFF8-4445-8A4D-4767FE610D3C@uva.nl> (raw)
On Feb 20, 2009, at 5:33 PM, Russell Adams wrote:
> On Fri, Feb 20, 2009 at 11:05:03AM +0100, Carsten Dominik wrote:
>> On Feb 19, 2009, at 9:02 PM, Russell Adams wrote:
>>> I was thinking of just exporting all key/value pairs in the header
>>> an org prefix (no - or _ or /, ie: "orgAUTHOR").
>> OK, try
>> (setq org-export-latex-import-inbuffer-stuff t)
> That worked, the only point I may make would be to exclude
> LATEX_HEADER and TEXT from that list.
OK, done. I think it would even make sense to remove OPTIONS,
I cannot see how you would use this, would you?
> I'm also trying to resolve an ordering issue. I want to have a
> header/footer line declared in the header, but I want to use these
> orgTITLE macros in that. Currently LATEX_HEADER and the class go first
> before the definitions, and TEXT occurs inside the document. If the
> macro isn't defined before the header/footer, you get an error.
> I may have to manually code those, which defeats the purpose of using
> the org options.
I have switched this around, these definitions now com right
after the \usepackage macros, before the custom header stuff.
next prev parent reply other threads:[~2009-02-21 13:04 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-02-15 6:59 FR: Define Latex macros from export header Russell Adams
2009-02-19 19:24 ` Carsten Dominik
2009-02-19 20:02 ` Russell Adams
2009-02-20 10:05 ` Carsten Dominik
2009-02-20 16:33 ` Russell Adams
2009-02-21 13:03 ` Carsten Dominik [this message]
2009-02-21 14:28 ` Russell Adams
2009-02-22 18:26 ` Latex features Russell Adams
2009-02-22 19:51 ` Carsten Dominik
2009-02-23 0:06 ` FR: Define Latex macros from export header Russell Adams
2009-02-26 20:19 ` Carsten Dominik
2009-02-26 21:26 ` Russell Adams
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:
List information: https://www.orgmode.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
* 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
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).