From: Wolfgang Schuster <schuster.wolfgang@googlemail.com>
To: mailing list for ConTeXt users <ntg-context@ntg.nl>
Subject: \setupenumeration(s) was: defineenumeration does not work with MKIV
Date: Mon, 4 Jan 2010 23:50:06 +0100 [thread overview]
Message-ID: <69897EFA-9BA3-44CB-8588-CE6A7D1B51FF@googlemail.com> (raw)
In-Reply-To: <3b4b12311001041436x3983c71bpc1ddee3e0d5d8ede@mail.gmail.com>
Sorry to hijack your post and since we're already there, why are \setupenumerations
and \setupdescriptions written in the plural form.
> \setupenumerations[problem][stopper=)]
When I would follow the system from other setup commands in context
i expect as correct names \setupenumeration and \setupdescription.
Wolfgang
___________________________________________________________________________________
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
___________________________________________________________________________________
next prev parent reply other threads:[~2010-01-04 22:50 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-01-04 22:36 defineenumeration does not work with MKIV. Works with MKII Curiouslearn
2010-01-04 22:50 ` Wolfgang Schuster [this message]
2010-01-05 4:08 ` \setupenumeration(s) was: defineenumeration does not work with MKIV Vladimir Lomov
2010-01-05 8:27 ` Wolfgang Schuster
2010-01-05 4:03 ` defineenumeration does not work with MKIV. Works with MKII Vladimir Lomov
2010-01-05 13:22 ` Curiouslearn
2010-01-05 13:52 ` Wolfgang Schuster
2010-01-05 13:56 ` Curiouslearn
2010-01-05 13:56 ` Vladimir Lomov
2010-01-05 14:14 ` Wolfgang Schuster
2010-01-05 14:22 ` Vladimir Lomov
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=69897EFA-9BA3-44CB-8588-CE6A7D1B51FF@googlemail.com \
--to=schuster.wolfgang@googlemail.com \
--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).