From: Hans Hagen <pragma@wxs.nl>
To: mailing list for ConTeXt users <ntg-context@ntg.nl>
Subject: Re: parameters to \startxmlsetups
Date: Tue, 07 May 2013 13:00:05 +0200 [thread overview]
Message-ID: <5188DEB5.3080103@wxs.nl> (raw)
In-Reply-To: <B1937B21-6399-4DC7-BD62-2CF7BE339034@uva.nl>
On 5/7/2013 12:18 PM, Meer, H. van der wrote:
> \startxmlsetups takes one (implicit) parameter #1, the current node.
> The setup can be called with \setup{node}{command}.
>
> My question: Can there be another parameter transferred to the \startxmlsetups from the \setup call?
no
> What I would like to do is having a variant \startxmlsetups and corresponding \setup with three parameters {#1}{#2}{#3}. Then argument #3 will allow me to transfer extraneous information to the \startxmlsetups. So one can avoid transferring information through (global) defines, which makes code less general and not very transparant.
best wrap it in a macro then
-----------------------------------------------------------------
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:[~2013-05-07 11:00 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-05-07 10:18 Meer, H. van der
2013-05-07 11:00 ` 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=5188DEB5.3080103@wxs.nl \
--to=pragma@wxs.nl \
--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).