From: Damien Thiriet <damien@thiriet.web4me.fr>
To: ntg-context@ntg.nl
Subject: line break after \item, but not \stopitem
Date: Tue, 9 Oct 2018 09:21:28 +0200 [thread overview]
Message-ID: <20181009072128.GA12695@maroilles.home> (raw)
Hi list,
I am designing a presentation for my pupils (some loooong exercices to
learn LibreOfficeDraw by doing). To be sure that they don't misview any
question, I decided to force a pagebreak after each first level item.
A question on TSE gave me the proper key to \setupitemize, but I am
facing an issue I didn't expect.
Given this MWE
\setuppapersize[S6]
\setupitemize[1][inbetween={\page}]
\starttext
\startitemize[n]
\startitem \input knuth
\stopitem
\startitem \input ward
\startitemize[a]
\startitem first point \stopitem
\startitem second point \stopitem
\stopitem
\stopitemize
\stoptext
I expected a page break after each 1 level \stopitem, that is after
knuth's text and "second point". However the text is breaking before
first point, that is at the beginning of level 2 startitemize, which is
AFAIK semantically part of a level 1 item.
Do you have any idea to force page break *after* "second point" and not
*before* "first point" ?
Thanks,
Damien Thiriet
___________________________________________________________________________________
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:[~2018-10-09 7:21 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-10-09 7:21 Damien Thiriet [this message]
2018-10-09 8:28 ` Hans Hagen
2018-10-09 17:41 ` Damien Thiriet
2018-10-09 19:07 ` 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=20181009072128.GA12695@maroilles.home \
--to=damien@thiriet.web4me.fr \
--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).