From: Russell Adams <RLAdams@AdamsInfoServ.Com>
To: emacs-orgmode@gnu.org
Subject: Re: Re: defining LaTeX macros that work inline and at export
Date: Thu, 21 May 2009 17:28:46 -0500 [thread overview]
Message-ID: <20090521222846.GI10324@thinkpad.adamsinfoserv.com> (raw)
In-Reply-To: <loom.20090521T220418-432@post.gmane.org>
Gray,
Yes, exporting will convert those variables inline, however, you could
include an area to define them in your header. Then again, if thats
the case, you may just want to stick to adding them into #+LATEX_HEADER.
On Thu, May 21, 2009 at 10:08:21PM +0000, Gray Calhoun wrote:
> > On Thu, May 21, 2009 at 05:13:41PM +0000, Gray Calhoun wrote:
>
> > > I'd like to define LaTeX macros that display correctly when they're
> > > embedded in an org file and are preserved when I export that file to LaTeX.
> > > Right now, I've added the LaTeX macros to org-format-latex-header, and
> > > repeated the macros in a #+LATEX_HEADER: comment. The two drawbacks of
> > > this approach are that I'd prefer to have most of the macros be
> > > file-specific and that I'd like to avoid duplicating these LaTeX commands.
> <- cut the rest ->
>
> Russell Adams <RLAdams <at> AdamsInfoServ.Com> writes:
>
> >
> > Couldn't you use the {{{macro}}} expansion in the export header? I
> > believe you can make your own.
> >
>
> Hi Russell,
>
> Thanks for the suggestion!
>
> I'm going to need to work with the LaTeX files themselves after writing
> and editing the drafts in org mode, so I want the macros to stick
> around after exporting the org file to LaTeX. My understanding is
> that the {{{macro}}} approach would expand the macros during that
> export.
>
> Best,
> Gray
>
>
>
> _______________________________________________
> 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
prev parent reply other threads:[~2009-05-21 22:29 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-05-21 17:13 defining LaTeX macros that work inline and at export Gray Calhoun
2009-05-21 17:28 ` Russell Adams
2009-05-21 22:08 ` Gray Calhoun
2009-05-21 22:28 ` Russell Adams [this message]
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=20090521222846.GI10324@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).