emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Russell Adams <RLAdams@AdamsInfoServ.Com>
To: emacs-orgmode@gnu.org
Subject: Re: FR: Define Latex macros from export header
Date: Sun, 22 Feb 2009 18:06:41 -0600	[thread overview]
Message-ID: <20090223000641.GL14026@thinkpad.adamsinfoserv.com> (raw)
In-Reply-To: <20090221142813.GH14026@thinkpad.adamsinfoserv.com>

On Sat, Feb 21, 2009 at 08:28:13AM -0600, Russell Adams wrote:
> >> 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 think I got it! The issue here is that we're trying to define a
_Latex_ macro with the export options, and THAT is where the
resolution order becomes an issue.

Could we create some org-export macros that will be translated inline?
That way the header data would be replaced in the body of all export
types (ascii, html, & latex)? No more need to define latex macros.

------- Example ------------

#+TITLE: This is a title
...
Welcome to %%orgTITLE%%.

after export:

Welcome to This is a title.

----------------------------

This resolves the ordering issue and lets the metadata be used in the
document, which is the original purpose.

The syntax would require some consideration, but anything fairly
obtuse that wouldn't be confused for a code sample would work. I like
"closing" formats and would prefer multiple symbols be involved to
minimize the chance of a collision. We'd likely need a OPTION for
whether or not to honor these.

Suggested formats:

 - %%orgVAR%%
 - (-:orgVAR:-) (credit to johnw for "Entranced by Smileys Format")
 - !~orgVAR~!

I need to learn lisp so I can start helping with these. :P

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

  parent reply	other threads:[~2009-02-23  0:06 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-02-15  6:59 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
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             ` Russell Adams [this message]
2009-02-26 20:19               ` FR: Define Latex macros from export header 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=20090223000641.GL14026@thinkpad.adamsinfoserv.com \
    --to=rladams@adamsinfoserv.com \
    --cc=emacs-orgmode@gnu.org \
    --subject='Re: FR: Define Latex macros from export header' \
    /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

Code repositories for project(s) associated with this 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).