From: "Meer, H. van der" <H.vanderMeer@uva.nl>
To: ConTeXt NTG <ntg-context@ntg.nl>
Subject: itemize behaviour
Date: Tue, 3 Jul 2012 19:43:34 +0000 [thread overview]
Message-ID: <C51359CE-8C7E-4130-8D13-07A6D04D51D2@uva.nl> (raw)
[-- Attachment #1.1: Type: text/plain, Size: 1804 bytes --]
I do not understand the workings of the itemize.
What I want is two nested itemlists. The outer one unpacked, the inner one packed. In the inner one the itemlist should be joinedup with the text before it.
I do not get this working, see the examples. The inner list is separated from the "Intro to inner list". It looks like the joinedup in the second example has no effect, because deleting it makes no difference. Switching the joinedup over to the outer itemize in the third example pulls everything together and destroys the unpacked of the first list.
How to achieve the following?
----------------------------------
- Intro to inner list
o one inner list
o two inner list
- second outer item
----------------------------------
Hans van der Meer
\starttext
\setupitemgroup[itemize][1][unpacked][symbol=4]
\setupitemgroup[itemize][2][unpacked][symbol=5]
\startitemize
\startitem
Intro to inner list.
\startitemize
\startitem one inner list \stopitem
\startitem two inner list \stopitem
\stopitemize
\stopitem
\startitem second outer item \stopitem
\stopitemize
\blank\thinrule\blank
\setupitemgroup[itemize][1][unpacked][symbol=4]
\setupitemgroup[itemize][2][packed,joinedup][symbol=5]
\startitemize
\startitem
Intro to inner list.
\startitemize
\startitem one inner list \stopitem
\startitem two inner list \stopitem
\stopitemize
\stopitem
\startitem second outer item \stopitem
\stopitemize
\blank\thinrule\blank
\setupitemgroup[itemize][1][unpacked,joinedup][symbol=4]
\setupitemgroup[itemize][2][packed][symbol=5]
\startitemize
\startitem
Intro to inner list.
\startitemize
\startitem one inner list \stopitem
\startitem two inner list \stopitem
\stopitemize
\stopitem
\startitem second outer item \stopitem
\stopitemize
\stoptext
[-- Attachment #1.2: Type: text/html, Size: 6352 bytes --]
[-- Attachment #2: itemize.pdf --]
[-- Type: application/pdf, Size: 11963 bytes --]
[-- Attachment #3: 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
___________________________________________________________________________________
next reply other threads:[~2012-07-03 19:43 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-07-03 19:43 Meer, H. van der [this message]
2012-07-05 18:16 ` Wolfgang Schuster
2012-07-05 19:47 ` Meer, H. van der
2012-07-06 4:49 ` Wolfgang Schuster
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=C51359CE-8C7E-4130-8D13-07A6D04D51D2@uva.nl \
--to=h.vandermeer@uva.nl \
--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).