From: Marco Patzer <lists@homerow.info>
To: ntg-context@ntg.nl
Subject: Re: Defining multiple enumerations fails
Date: Fri, 20 Sep 2013 11:10:06 +0200 [thread overview]
Message-ID: <20130920091005.GC6757@homerow> (raw)
In-Reply-To: <523B7F37.5020901@wxs.nl>
[-- Attachment #1.1: Type: text/plain, Size: 734 bytes --]
On 2013–09–20 Hans Hagen wrote:
> On 9/20/2013 12:33 AM, Marco Patzer wrote:
> >Hi,
> >
> >defining multiple enumerations at the same time used to work. Is
> >this syntax not supported any longer or is it a bug?
> >
> >\defineenumeration [foo, bar]
> >\starttext
> > \foo foo\par
> > \bar bar\par
> >\stoptext
>
> This multiple defining was only supported for a few commands and
> made the new commandhandler code too complex.
So I conclude that multiple definitions are now deprecated.
> In the meantime inheritance is rather consistent so the new way
> is:
>
> \defineenumeration [foo]
> \defineenumeration [bar] [foo]
Note that this is not the same as \defineenumeration [foo, bar]
Marco
[-- Attachment #1.2: Digital signature --]
[-- Type: application/pgp-signature, Size: 490 bytes --]
[-- Attachment #2: Type: text/plain, Size: 485 bytes --]
___________________________________________________________________________________
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
___________________________________________________________________________________
prev parent reply other threads:[~2013-09-20 9:10 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-09-19 22:33 Marco Patzer
2013-09-19 22:48 ` Hans Hagen
2013-09-20 9:10 ` Marco Patzer [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=20130920091005.GC6757@homerow \
--to=lists@homerow.info \
--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).