From: Alan BRASLAU <alan.braslau@cea.fr>
To: Taco Hoekwater <taco@elvenkind.com>,
mailing list for ConTeXt users <ntg-context@ntg.nl>
Subject: Re: Removing Introduction section number
Date: Mon, 14 Jun 2010 15:40:13 +0200 [thread overview]
Message-ID: <201006141540.14065.alan.braslau@cea.fr> (raw)
In-Reply-To: <4C160FE2.4000409@elvenkind.com>
On Monday 14 June 2010 13:17:54 Taco Hoekwater wrote:
> Hi Alan,
>
> Alan BRASLAU wrote:
> > I have to say that I am now a bit confused about the use of arguments in
> > ConTeXt.
>
> The general rule is quite straightforward:
>
> * arguments in {} pairs are typeset material
> * arguments in [] are setup instructions and metadata
>
> Whether or not an argument is optional has nothing to
> do with the used delimiters.
Quite logical and straightforward.
It is useful to read the manual (section 1.3):
"A command is often followed by setups or by text. Setups
are placed between brackets ([]). The scope or range of
the command, the text acted upon, is placed between
curly brackets ({})."
...
I see that my reflexes have been spoiled by years of practice with LaTeX - old
habits die hard.
Lamport (section 2.5):
"Command arguments are enclosed in curly braces { and },
except for optional arguments, which are enclosed in square
brackets [ and ]."
So I added a paragraph to
http://wiki.contextgarden.net/From_LaTeX_to_ConTeXt#Command_syntax
Alan
___________________________________________________________________________________
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-06-14 13:40 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-06-13 20:08 Vyatcheslav Yatskovsky
2010-06-14 6:52 ` Taco Hoekwater
2010-06-14 7:39 ` Alan BRASLAU
2010-06-14 7:54 ` Taco Hoekwater
2010-06-14 8:04 ` Alan BRASLAU
2010-06-14 8:14 ` Taco Hoekwater
2010-06-14 9:52 ` Hans Hagen
2010-06-14 10:14 ` Peter Münster
2010-06-14 10:21 ` Hans Hagen
2010-06-14 10:27 ` John Haltiwanger
2010-06-14 10:30 ` Alan BRASLAU
2010-06-14 11:17 ` Taco Hoekwater
2010-06-14 13:40 ` Alan BRASLAU [this message]
2010-06-14 13:55 ` Hans Hagen
2010-06-14 10:12 ` Hans Hagen
[not found] <mailman.1702.1276514035.4277.ntg-context@ntg.nl>
2010-06-14 11:18 ` Vyatcheslav Yatskovsky
[not found] <mailman.0.1276509602.1911.ntg-context@ntg.nl>
2010-06-14 10:54 ` Vyatcheslav Yatskovsky
[not found] <mailman.1480.1275862490.4277.ntg-context@ntg.nl>
2010-06-06 22:21 ` Vyatcheslav Yatskovsky
2010-06-06 22:23 ` Vyatcheslav Yatskovsky
2010-06-07 22:00 ` Rogutės Sparnuotos
[not found] <mailman.1477.1275853449.4277.ntg-context@ntg.nl>
2010-06-06 20:57 ` Vyatcheslav Yatskovsky
2010-06-06 21:15 ` Wolfgang Schuster
2010-06-13 20:03 ` Vyatcheslav Yatskovsky
2010-06-14 6:48 ` Taco Hoekwater
2010-06-14 12:27 ` Wolfgang Schuster
2010-06-14 12:30 ` Vyatcheslav Yatskovsky
2010-06-06 21:20 ` Yury G. Kudryashov
2010-06-06 21:46 ` Alan BRASLAU
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=201006141540.14065.alan.braslau@cea.fr \
--to=alan.braslau@cea.fr \
--cc=ntg-context@ntg.nl \
--cc=taco@elvenkind.com \
/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).