ntg-context - mailing list for ConTeXt users
 help / color / mirror / Atom feed
From: "Adam Lindsay" <atl@comp.lancs.ac.uk>
Subject: Re: Not possible to redefine inbetween in \definedescription
Date: Thu, 14 Jul 2005 16:08:02 +0100	[thread overview]
Message-ID: <20050714150802.20787@mail.comp.lancs.ac.uk> (raw)
In-Reply-To: <42D676F2.2080506@elvenkind.com>

Taco Hoekwater said this at Thu, 14 Jul 2005 16:30:10 +0200:

>> So every command with brackets needs to be grouped? Maybe something 
>> else? Where to look at it?
>
>I know of nothing else, just brackets. Any bracket, not just as
>part of a command, but also in cases like this:
>
>   \setuppublications[left={[}]

Ooh, just remembered: Commas, too. 
\setupitemize[stopper={,}]

and to be sure: "every command with brackets" sounds like you mean
everywhere... this is just amongst parameters.

So: brackets and commas, used as parameter values, need to have
enclosing braces.

If you think of the braces as "quoting" the parameter values, you'll
probably be alright.
-- 
=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
 Adam T. Lindsay, Computing Dept.     atl@comp.lancs.ac.uk
 Lancaster University, InfoLab21        +44(0)1524/510.514
 Lancaster, LA1 4WA, UK             Fax:+44(0)1524/510.492
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-

  reply	other threads:[~2005-07-14 15:08 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-07-14 11:43 Radhelorn
2005-07-14 12:45 ` Taco Hoekwater
2005-07-14 13:53   ` Radhelorn
2005-07-14 14:30     ` Taco Hoekwater
2005-07-14 15:08       ` Adam Lindsay [this message]
2005-07-14 17:25         ` Radhelorn
2005-07-14 17:27           ` Adam Lindsay
2005-07-14 17:49           ` Christopher Creutzig
2005-07-15  5:13             ` Radhelorn
2005-07-14 15:01     ` luigi.scarso
2005-07-20 19:58 ` Hans Hagen

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=20050714150802.20787@mail.comp.lancs.ac.uk \
    --to=atl@comp.lancs.ac.uk \
    --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).