Hi Peter, hi all!

On 2010-04-17 <08:52:05>, Peter Münster wrote:
> On Fri, Apr 16 2010, Philipp Gesang wrote:
> 
> > I'd naively expect \track#1 to behave identically regardless of
> > interaction.  How do I make it interaction-proof
> 
> Sorry, I had forgotten to answer your main-question:
> 
> \def\foottrack#1{\expanded{\footnote{\ctxlua{track.simple("#1")}}}}
Thanks very much, this does it!

> > and, if possible, how do I interaction-proof macros in general?
> 
> I don't know, but I suppose \expanded{} can help in most cases.  

Adding that one to my “try first”-list seems reasonable. There's a macro
\expanded defined in syst-aux.mkiv but it mentions certain “recent TeXs”
that have it builtin as a primitive -- which one am I using in mkiv?
The LuaTeXbook mentions an extra primitive “\expanded” taken from
pdfTeX. Are they equivalent?

Thanks a lot for your help!


Philipp


> Cheers, Peter
> 
> -- 
> Contact information: http://pmrb.free.fr/contact/
> 
> 
> ___________________________________________________________________________________
> If your question is of interest to others as well, please add an entry to the 
> Wiki!
> 
> maillist : ntg-context@ntg.nl / http://www.ntg.nl/mailman/listinfo/ntg-context
> webpage  : http://www.pragma-ade.nl / http://tex.aanhet.net
> archive  : http://foundry.supelec.fr/projects/contextrev/
> wiki     : http://contextgarden.net
> ___________________________________________________________________________________

-- 
()  ascii ribbon campaign - against html e-mail
/\  www.asciiribbon.org   - against proprietary attachments

Attachment: signature.asc
Description: Digital signature

___________________________________________________________________________________
If your question is of interest to others as well, please add an entry to the 
Wiki!

maillist : ntg-context@ntg.nl / http://www.ntg.nl/mailman/listinfo/ntg-context
webpage  : http://www.pragma-ade.nl / http://tex.aanhet.net
archive  : http://foundry.supelec.fr/projects/contextrev/
wiki     : http://contextgarden.net
___________________________________________________________________________________

Reply via email to