From: Hans Hagen <pragma@wxs.nl>
To: mailing list for ConTeXt users <ntg-context@ntg.nl>
Cc: Philipp Gesang <pgesang@ix.urz.uni-heidelberg.de>
Subject: Re: lua, footnotes, interaction
Date: Sat, 17 Apr 2010 12:37:23 +0200 [thread overview]
Message-ID: <4BC98F63.2090806@wxs.nl> (raw)
In-Reply-To: <20100417072041.GA25161@localhost.localdomain>
On 17-4-2010 9:20, Philipp Gesang wrote:
> 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?
no, we had \expanded (and \protected and \unexpanded and ...) long
before they showed up as primitives
when \expanded was added, it was agreed that that name could be used
even if it clashed with context internals; ok, it add confusion for
users who use low level code, but as we always have \normalexpanded in
context it's no big deal; when in doubt, use \normal* for primitives (or
\primitive\expanded)
Hans
-----------------------------------------------------------------
Hans Hagen | PRAGMA ADE
Ridderstraat 27 | 8061 GH Hasselt | The Netherlands
tel: 038 477 53 69 | voip: 087 875 68 74 | www.pragma-ade.com
| www.pragma-pod.nl
-----------------------------------------------------------------
___________________________________________________________________________________
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
___________________________________________________________________________________
prev parent reply other threads:[~2010-04-17 10:37 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-04-16 21:10 Philipp Gesang
2010-04-17 6:27 ` Peter Münster
2010-04-17 10:19 ` Hans Hagen
2010-04-17 6:52 ` Peter Münster
2010-04-17 7:20 ` Philipp Gesang
2010-04-17 10:37 ` Hans Hagen [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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=4BC98F63.2090806@wxs.nl \
--to=pragma@wxs.nl \
--cc=ntg-context@ntg.nl \
--cc=pgesang@ix.urz.uni-heidelberg.de \
/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.
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 NNTP newsgroup(s).