Re: FR: Define Latex macros from export header

From: Russell Adams <RLAdams@AdamsInfoServ.Com>
To: emacs-orgmode@gnu.org
Subject: Re: FR: Define Latex macros from export header
Date: Thu, 26 Feb 2009 15:26:10 -0600	[thread overview]
Message-ID: <20090226212610.GJ18720@thinkpad.adamsinfoserv.com> (raw)
In-Reply-To: <E6EAC781-BD66-40D3-89F2-68630FE3BA28@uva.nl>

Carsten,

Rock on! I'll test this out shortly.

Thanks.

On Thu, Feb 26, 2009 at 09:19:48PM +0100, Carsten Dominik wrote:
> Hi Russel,
>
> you can now write {{{TITLE}}} and {{{EMAIL}}} etc to get these  
> interpolated.
> More generally, you can write
>
> #+MACRO: name value of the macro
>
> and then write {{{name}}} to get the value interpolated.
>
> - Carsten
>
> On Feb 23, 2009, at 1:06 AM, Russell Adams wrote:
>
>> 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
>>
>>
>> _______________________________________________
>> 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