From: Wolfgang Schuster <schuster.wolfgang@googlemail.com>
To: mailing list for ConTeXt users <ntg-context@ntg.nl>
Subject: Re: checking for module parameters
Date: Fri, 13 Aug 2010 05:16:40 +0200 [thread overview]
Message-ID: <4C64B918.8050504@googlemail.com> (raw)
In-Reply-To: <20100812222047.GB18623@aides>
Am 13.08.10 00:20, schrieb Philipp Gesang:
> Hi,
>
> is there a way to check whether an option was specified through \usemodule?
> Couldn't find anything like that in core-fil.mkiv.
>
> I'd imagined some branching as with the system macros:
>
> ······ Wishful thinking ·······················································
>
> \doifmoduleparameter{modulename}{key} % in the module code
> {\somecommand[\moduleparameter{modulename}{key}]}
>
> \usemodule % user code
> [modulename]
> [key=val]
>
> ····· /Wishful thinking ·······················································
>
> Thanks for any suggestions,
You can set a empty value for the kay in your module and check if the
user has set a value with \usemodule:
\setupmodule[key=]
\doifsomething{\currentmoduleparameter{key}}{\setupsomething[key=\currentmoduleparameter{key}]}
For a better answer i have to know for what purpose you need this
information.
Wolfgang
___________________________________________________________________________________
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-08-13 3:16 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-08-12 22:20 Philipp Gesang
2010-08-13 3:16 ` Wolfgang Schuster [this message]
2010-08-13 8:31 ` Philipp Gesang
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=4C64B918.8050504@googlemail.com \
--to=schuster.wolfgang@googlemail.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).