ntg-context - mailing list for ConTeXt users
 help / color / mirror / Atom feed
From: "Thomas A. Schmitz" <thomas.schmitz@uni-bonn.de>
To: mailing list for ConTeXt users <ntg-context@ntg.nl>
Subject: Re: defining (new) macros with optional arguments
Date: Wed, 10 Sep 2008 12:26:19 +0200	[thread overview]
Message-ID: <E84315C0-ED9B-4531-8F14-8EB2D3F1C1E0@uni-bonn.de> (raw)
In-Reply-To: <CBB3636EB677D345A9A354D258233415BF0EFE@deimsg12.de.net.world>


On Sep 10, 2008, at 11:54 AM, Goebel, Juergen wrote:

> Hi,
>
> Does something like \newcommand exist in ConTeXt?
> My questions aims especially at the optional argument
> with a predefined value.  So, how do I realize
>
> \newcommand{\test}[2][A]{foo}
>
> with ConTeXt. In the fine manual I found an index entry
> \definecommand, but in the 'rest' of the manual it was
> never mentioned (print and screen version alike)!
>
> Regards,
>
> Juergen
>
No, we never define any commands... Err, in fact yes, sometimes we do.  
You want to read http://wiki.contextgarden.net/System_Macros ,  
especially http://wiki.contextgarden.net/System_Macros/Handling_Arguments

HTH

Thomas
___________________________________________________________________________________
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  : https://foundry.supelec.fr/projects/contextrev/
wiki     : http://contextgarden.net
___________________________________________________________________________________


  reply	other threads:[~2008-09-10 10:26 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-09-10  9:54 Goebel, Juergen
2008-09-10 10:26 ` Thomas A. Schmitz [this message]
2008-09-10 10:36   ` Wolfgang Schuster

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=E84315C0-ED9B-4531-8F14-8EB2D3F1C1E0@uni-bonn.de \
    --to=thomas.schmitz@uni-bonn.de \
    --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).