From: Wolfgang Schuster <schuster.wolfgang@gmail.com>
To: mailing list for ConTeXt users <ntg-context@ntg.nl>
Subject: Re: setupenumerations overwriting setupitemize
Date: Thu, 20 Feb 2014 14:52:24 +0100 [thread overview]
Message-ID: <958EDBE0-3C48-4ADA-9305-D30623023B24@gmail.com> (raw)
In-Reply-To: <CA+cORN_efgEzUkg5mtb7mDoxyHA6sRYqRafTdMpLxdmFEe2vbw@mail.gmail.com>
Am 20.02.2014 um 14:45 schrieb Thomas Möbius <kontakt@thomasmoebius.de>:
> A general question. I use setupenumerations to define theorem-,
> lemma-, and definition-environments for my document. I realised that
> setupenumerations is overwriting keys that are set in setupitemize
> (and groups defined by defineitemgroup).
>
> ~~~snip~~~
> \setupenumerations [numberconversion=numbers]
>
> \starttext
> \startitemize[a]
> \item Text Text
> \item Text Text
> \stopitemize
> \stoptext
> ~~~snip~~~
>
> vs.
>
> ~~~snip~~~
> %\setupenumerations [numberconversion=numbers]
>
> \starttext
> \startitemize[a]
> \item Text Text
> \item Text Text
> \stopitemize
> \stoptext
> ~~~snip~~~
>
> This is unintuitive for me.. Is this expected behavior??
What is the problem, I can’t see a difference in the output of both examples?
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:[~2014-02-20 13:52 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-02-20 13:45 Thomas Möbius
2014-02-20 13:52 ` Wolfgang Schuster [this message]
2014-02-20 14:09 ` Thomas Friedrich
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=958EDBE0-3C48-4ADA-9305-D30623023B24@gmail.com \
--to=schuster.wolfgang@gmail.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).