From: "Vianney le Clément" <vleclement@gmail.com>
To: mailing list for ConTeXt users <ntg-context@ntg.nl>
Subject: Re: processaction inside MP graphic
Date: Thu, 13 May 2010 10:45:26 +0200 [thread overview]
Message-ID: <AANLkTimmDcBfoMMimsCdil6Ghem8DlVTMZWdXcNpdXoX@mail.gmail.com> (raw)
In-Reply-To: <4BEBAA96.7020108@elvenkind.com>
On Thu, May 13, 2010 at 09:30, Taco Hoekwater <taco@elvenkind.com> wrote:
> Like many of the more complex commands, \processaction does not
> expand totally. If you are using mkiv, you could define \Shape
> like this:
>
> \def\Shape#1%
> {\directlua{
> local known = {square = 'unitsquare', circle = 'unitcircle' }
> tex.sprint(known[#1] or 'unitsquare')}}
Thanks Taco. That does the trick provided you enclose #1 with quotes:
\def\Shape#1%
{\directlua{
local known = {square = 'unitsquare', circle = 'unitcircle' }
tex.sprint(known['#1'] or 'unitsquare')}}
Another, maybe uglier but plain TeX, solution I've come up with is
defining auxiliary macros:
\def\ShapeSSSsquare{unitsquare}
\def\ShapeSSScircle{unitcircle}
\def\Shape#1{\csname ShapeSSS#1\endcsname}
But of course, this does not handle unknown options (though that could
be added).
I'll add this to the wiki.
Vianney
___________________________________________________________________________________
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
___________________________________________________________________________________
next prev parent reply other threads:[~2010-05-13 8:45 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-05-12 17:22 Vianney le Clément
2010-05-13 7:30 ` Taco Hoekwater
2010-05-13 8:45 ` Vianney le Clément [this message]
2010-05-13 9:13 ` luigi scarso
2010-05-13 9:19 ` Hans Hagen
2010-05-13 11:04 ` Vianney le Clément
2010-05-13 11:12 ` luigi scarso
2010-05-13 11:16 ` Vianney le Clément
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=AANLkTimmDcBfoMMimsCdil6Ghem8DlVTMZWdXcNpdXoX@mail.gmail.com \
--to=vleclement@gmail.com \
--cc=ntg-context@ntg.nl \
/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).