ntg-context - mailing list for ConTeXt users
 help / color / mirror / Atom feed
From: Sanjoy Mahajan <sanjoy@mrao.cam.ac.uk>
Subject: syntax for numbercommand and \gobbleoneargument
Date: Thu, 20 Apr 2006 15:09:30 -0400	[thread overview]
Message-ID: <E1FWeWw-0007CY-Ni@approximate.corpus.cam.ac.uk> (raw)

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]:

\setuphead[chapter][numbercommand={\gobbleoneargument},
]

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?

The error is (with tex : pdfeTeX, 3.141592-1.21a-2.2 (Web2C 7.5.4),
context : ver: 2006.04.17 23:14):

ERROR: Argument of \gobbleoneargument has an extra }.

--- TeX said ---
<inserted text> 
                \par 
<to be read again> 
                   }
\@@kochapternumbercommand ->{\gobbleoneargument }
                                                  
<argument> ...{\??ko \v!chapter \c!numbercommand }
                                                  {\setstrut \begstrut \exec...

\@@ko::normal ...numbercontent \setbox 0\hbox {{#1
                                                  }\hskip \numberheaddistanc...

\doplaceheadnumbertext ...utes \dostopattributes }
                                                  }\fi \endheadplacement {#1...
...
l.4 \chapter{One}

             reply	other threads:[~2006-04-20 19:09 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-04-20 19:09 Sanjoy Mahajan [this message]
2006-04-20 19:53 ` Peter Münster
2006-04-20 20:42   ` Sanjoy Mahajan
2006-04-20 20:55 ` 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=E1FWeWw-0007CY-Ni@approximate.corpus.cam.ac.uk \
    --to=sanjoy@mrao.cam.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).