From: Wolfgang Schuster <schuster.wolfgang@googlemail.com>
To: mailing list for ConTeXt users <ntg-context@ntg.nl>
Subject: Re: \define[1]\command or \define\command[1]? (was: math: command for absolute value: `\define\abs[1]{\lvert #1 \rvert}` throws `\lvert ->\Udelimiter`.)
Date: Sun, 5 Jun 2011 12:16:43 +0200 [thread overview]
Message-ID: <6DBE182C-299D-4A18-8864-896F4B21853E@googlemail.com> (raw)
In-Reply-To: <1307268662.28001.2.camel@mattotaupa>
Am 05.06.2011 um 12:11 schrieb Paul Menzel:
> thank you very much for the solution. I took my definition from the Wiki [1].
>
> Could the developers please clarify the correct syntax so that it can be
> updated in the source or the Wiki.
The wiki entry is correct, the syntax is
\define[<number of arguments>]\<name of the command>{<do something with the arguments>}
When you want a command without argument you can omit the brackets and write
\define\command{...}
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:[~2011-06-05 10:16 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-06-04 20:40 math: command for absolute value: `\define\abs[1]{\lvert #1 \rvert}` throws `\lvert ->\Udelimiter` Paul Menzel
2011-06-04 20:51 ` Peter Münster
2011-06-04 21:59 ` Otared Kavian
2011-06-05 10:11 ` \define[1]\command or \define\command[1]? (was: math: command for absolute value: `\define\abs[1]{\lvert #1 \rvert}` throws `\lvert ->\Udelimiter`.) Paul Menzel
2011-06-05 10:15 ` [solved] " Paul Menzel
2011-06-05 10:16 ` Wolfgang Schuster [this message]
2011-06-29 2:37 ` Repeated Hyphens in URL Cause Fatal Error Raymond LeClair
2011-06-29 5:34 ` luigi scarso
2011-06-29 11:27 ` Netiquette (was: Repeated Hyphens in URL Cause Fatal Error) Paul Menzel
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=6DBE182C-299D-4A18-8864-896F4B21853E@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).