From: Hans van der Meer <H.vanderMeer@uva.nl>
To: NTG ConTeXt <ntg-context@ntg.nl>
Subject: itemize-margin->break joinedup
Date: Sun, 17 Jan 2010 13:46:58 +0100 [thread overview]
Message-ID: <B9DAB6D1-0BA4-4534-9A11-632AE15D02B1@uva.nl> (raw)
[-- Attachment #1: Type: text/plain, Size: 822 bytes --]
The joinedup parameter in \startitemize is meant to close the gap
between the list and the preceding material. The margin parameter is
for horizontal movement of the list, is I understand it. However,
addition of a margin to the \startitemize disables the joinedup. Is
this expected behaviour? Below is a minimal example showing the effect.
Hans van der Meer
\setupblank[small]
\setupitemize[n,packed]
\starttext
\contextversion\ After \type{\startitemize[joinedup]} joinedup ok:
\startitemize[joinedup]
\item sub a
\startitemize
\item sub a1
\item sub a2
\stopitemize
\item sub b
\stopitemize
\contextversion\ After type[joinedup,margin=2cm] joinedup ineffective:
\startitemize[joinedup,margin=2cm]
\item sub a
\startitemize
\item sub a1
\item sub a2
\stopitemize
\item sub b
\stopitemize
\stoptext
[-- Attachment #2: itemize.pdf --]
[-- Type: application/pdf, Size: 15491 bytes --]
[-- Attachment #3: Type: text/plain, Size: 7 bytes --]
[-- Attachment #4: Type: text/plain, Size: 486 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:[~2010-01-17 12:46 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-01-17 12:46 Hans van der Meer [this message]
2010-01-17 12:51 ` 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=B9DAB6D1-0BA4-4534-9A11-632AE15D02B1@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).