From: Taco Hoekwater <taco.hoekwater@wkap.nl>
Subject: Bug in \defineenumeration
Date: Thu, 01 Apr 1999 16:10:00 +0000 (/etc/localtime) [thread overview]
Message-ID: <14083.39512.709590.260550@localhost> (raw)
In-Reply-To: <000901be7c43$0ca44da0$0c01a8c1@worf.login-bv.com>
Hello Hans,
At least my version of context exhibits a rather nasty bug in
enumerations: \cap prevents the reading of the optional argument to
the defined command.
Try this little document (sorry, nl version):
\doornummeren[rommel][kopletter=kap]
\starttekst
\startrommel [-]
Wat tekst
\stoprommel
\tracingnone
\rommel[-]
Nog wat text
\stoptekst
How can I fix this?
Greetings, Taco
--
Taco Hoekwater taco.hoekwater@wkap.nl
Kluwer Academic Publishers -- Pre Press --
Achterom 119, 3311 KB Dordrecht, The Netherlands tel. 31-78-6392550
---------------------------------------------------------------------
next prev parent reply other threads:[~1999-04-01 16:10 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
1999-04-01 13:25 \definehead with some extra's Gilbert van den Dobbelsteen
1999-04-01 14:49 ` Hans Hagen
1999-04-01 16:10 ` Taco Hoekwater [this message]
1999-04-01 15:41 ` Bug in \defineenumeration Hans Hagen
1999-04-01 17:46 ` Taco Hoekwater
1999-04-01 16:36 ` Hans Hagen
1999-04-02 11:24 ` Taco Hoekwater
1999-04-02 11:58 ` Hans Hagen
1999-04-02 12:00 ` Hans Hagen
1999-04-02 13:14 ` 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=14083.39512.709590.260550@localhost \
--to=taco.hoekwater@wkap.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).