From: Hans Hagen <pragma@wxs.nl>
Subject: Re: syntax for numbercommand and \gobbleoneargument
Date: Thu, 20 Apr 2006 22:55:32 +0200 [thread overview]
Message-ID: <4447F544.4060901@wxs.nl> (raw)
In-Reply-To: <E1FWeWw-0007CY-Ni@approximate.corpus.cam.ac.uk>
Sanjoy Mahajan wrote:
> This minimal file [case 1]:
>
> \setuphead[chapter][numbercommand={\gobbleoneargument}
> ]
> \starttext
> \chapter{One}
> \stoptext
>
> fails. Whereas if the first two lines are replaced by [case 2]:
>
in this case the command is
"{\gobbleoneargument} "
and
{\gobbleoneargument} {some text}
will fail because gobble runs into an }
> \setuphead[chapter][numbercommand={\gobbleoneargument},
> ]
>
in this case the command is
{\gobbleoneargument"
and
\gobbleoneargument{some text}
work sok
> or [case 3]:
>
> \setuphead[chapter][numbercommand={\gobbleoneargument}]
>
> then it's fine. Is this a bug or a feature of TeX's tricky spacing
> rules? And how can I think about ConTeXt's parsing in way that the
> difference between cases 1 and 2,3 is obvious?
>
idem
it's
[key=value]
[key=value, nextkey=nextvalue]
(spaces are dropped after the comma) so in
[key=value ,nextkey=nextvalue]
the comma before the , is part of key's value
-----------------------------------------------------------------
Hans Hagen | PRAGMA ADE
Ridderstraat 27 | 8061 GH Hasselt | The Netherlands
tel: 038 477 53 69 | fax: 038 477 53 74 | www.pragma-ade.com
| www.pragma-pod.nl
-----------------------------------------------------------------
prev parent reply other threads:[~2006-04-20 20:55 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-04-20 19:09 Sanjoy Mahajan
2006-04-20 19:53 ` Peter Münster
2006-04-20 20:42 ` Sanjoy Mahajan
2006-04-20 20:55 ` Hans Hagen [this message]
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=4447F544.4060901@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).