From: Lawrence Bell <lawrence.matthew.bell@gmail.com>
To: ntg-context@ntg.nl
Subject: nested itemgroups sometimes not working
Date: Wed, 1 Feb 2017 15:43:20 +0000 [thread overview]
Message-ID: <CAL4oCsQnOGidPKER_xBzC=Ucs7UBMujk_5YjCSs6s=TYgxs1mg@mail.gmail.com> (raw)
[-- Attachment #1.1: Type: text/plain, Size: 1039 bytes --]
I'm having some difficulties with nested itemgroups. I've produced a
minimal working example as follows.
\defineitemgroup
[test] [symbol=n]
\starttext
% \startitemgroup
% \startitem
% \startitemgroup[test]
% \startitem
% ...
% \stopitem
% \stopitemgroup
% \stopitem
% \stopitemgroup
\startitemgroup
\startitem
\startitemgroup
\startitem
Lorem ipsum
\startitemgroup[test]
\startitem
dolor sit amet,
\stopitem
\startitem
consectetur adipisicing elit.
\stopitem
\stopitemgroup
\stopitem
\stopitemgroup
\stopitem
\stopitemgroup
\stoptext
I would expect items in the [test] itemgroup to be numbered 1, 2 but
instead they are both 0. I have also found out that, bizarrely,
uncommenting the first itemgroup fixes the issue. This is the behaviour I
get on the TeXLive 2016 version of ConTeXt, I don't have the latest
minimals installed to test.
Thanks in advance for any help with this matter!
[-- Attachment #1.2: Type: text/html, Size: 4453 bytes --]
[-- Attachment #2: Type: text/plain, Size: 492 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://context.aanhet.net
archive : https://bitbucket.org/phg/context-mirror/commits/
wiki : http://contextgarden.net
___________________________________________________________________________________
next reply other threads:[~2017-02-01 15:43 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-02-01 15:43 Lawrence Bell [this message]
2017-02-01 16:51 ` Henri Menke
2017-02-01 17:59 ` Lawrence Bell
2017-02-02 16:50 ` Pablo Rodriguez
2017-02-02 16:48 ` Pablo Rodriguez
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='CAL4oCsQnOGidPKER_xBzC=Ucs7UBMujk_5YjCSs6s=TYgxs1mg@mail.gmail.com' \
--to=lawrence.matthew.bell@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).