From: Hans Hagen <pragma@wxs.nl>
To: mailing list for ConTeXt users <ntg-context@ntg.nl>
Subject: Re: define vs setup
Date: Thu, 26 Jul 2012 10:13:35 +0200 [thread overview]
Message-ID: <5010FC2F.4080709@wxs.nl> (raw)
In-Reply-To: <5010B7D3.5040700@googlemail.com>
On 26-7-2012 05:21, S Barmeier wrote:
> You can \setup what you \define|d yourself and \setup what is
> pre\define|d, but not \setup something that is not \define|d.
>
> Maybe ;)
it depends .. often it's:
\definexx[whatever]
\definexx[whatever][settings]
\definexx[another][parent]
\definexx[another][parent][settings]
\setupxx[settings]
\setupxx[another][settings]
\setupxx[whatever][settings]
sometimes there are no defines because a feature is generic or global in
nature. often a define generates a command (\whatever, \startwhatever), etc
btw, a redefine does not reset already set parameters (in mkii that is
often the case but not in mkiv)
it all depends on what kind of functionality you're dealing with
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
___________________________________________________________________________________
next prev parent reply other threads:[~2012-07-26 8:13 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-07-26 3:18 Bill Meahan
2012-07-26 3:21 ` S Barmeier
2012-07-26 8:13 ` Hans Hagen [this message]
2012-07-26 15:04 ` Bill Meahan
2012-07-26 15:34 ` Marco Patzer
2012-07-26 15:40 ` Bill Meahan
2012-07-26 16:15 ` Mojca Miklavec
2012-07-26 16:21 ` Khaled Hosny
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=5010FC2F.4080709@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).