emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Russell Adams <RLAdams@AdamsInfoServ.Com>
To: emacs org-mode mailing list <emacs-orgmode@gnu.org>
Subject: Re: FR: Define Latex macros from export header
Date: Thu, 19 Feb 2009 14:02:49 -0600	[thread overview]
Message-ID: <20090219200249.GI17284@thinkpad.adamsinfoserv.com> (raw)
In-Reply-To: <693E9A38-E1AA-49BC-BB05-5ADFE2199A57@uva.nl>

Carsten,

I was thinking of just exporting all key/value pairs in the header with
an org prefix (no - or _ or /, ie: "orgAUTHOR").

We don't need to pick any specific ones. The only one that we have to
worry about is properly quoting the OPTIONS line.

FYI I love the LATEX_HEADER line, I've done away with the latex
classes entirely in some recent documents. Its not in the manual yet
though.

Thanks.

On Thu, Feb 19, 2009 at 08:24:39PM +0100, Carsten Dominik wrote:
> Hi Russel,
>
> can you come up with a complete list of macros you'd like
> to have defined?  Right now you are leaving the guesswork to me.
>
> - Carsten
>
> On Feb 15, 2009, at 7:59 AM, Russell Adams wrote:
>
>> I think this one should be very easy!
>>
>> For each option in the export template at the head of the file, could
>> we export them for use in Latex?
>>
>> For example:
>> #+AUTHOR:    Russell Adams
>>
>> becomes
>>
>> \def\ORG_AUTHOR{Russell Adams}
>>
>> in the header of the Latex output?
>>
>> I'm finding myself redefining these macros, especially when I'm using
>> a custom maketitle.
>>
>> Thanks.
>>
>> ------------------------------------------------------------------
>> Russell Adams                            RLAdams@AdamsInfoServ.com
>>
>> PGP Key ID:     0x1160DCB3           http://www.adamsinfoserv.com/
>>
>> Fingerprint:    1723 D8CA 4280 1EC9 557F  66E8 1154 E018 1160 DCB3
>>
>>
>> _______________________________________________
>> Emacs-orgmode mailing list
>> Remember: use `Reply All' to send replies to the list.
>> Emacs-orgmode@gnu.org
>> http://lists.gnu.org/mailman/listinfo/emacs-orgmode
>


------------------------------------------------------------------
Russell Adams                            RLAdams@AdamsInfoServ.com

PGP Key ID:     0x1160DCB3           http://www.adamsinfoserv.com/

Fingerprint:    1723 D8CA 4280 1EC9 557F  66E8 1154 E018 1160 DCB3

  reply	other threads:[~2009-02-19 20:02 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 [this message]
2009-02-20 10:05     ` Carsten Dominik
2009-02-20 16:33       ` Russell Adams
2009-02-21 13:03         ` Carsten Dominik
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

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=20090219200249.GI17284@thinkpad.adamsinfoserv.com \
    --to=rladams@adamsinfoserv.com \
    --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 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).