From: Bruce Horrocks <ntg@scorecrow.com>
To: "ntg-context@ntg.nl" <ntg-context@ntg.nl>
Subject: Orphan issue with \startitemize
Date: Thu, 26 Nov 2020 21:11:25 +0000 [thread overview]
Message-ID: <DD7B6251-0C04-4D64-8F58-6E05C10DB92D@scorecrow.com> (raw)
With the following MWE:
\def\Lorem{Lorem ipsum dolor sit amet, consectetur adipiscing
elit, sed do eiusmod tempor incididunt ut labore et dolore
magna aliqua. Ut enim ad minim veniam, quis nostrud exercitation
ullamco laboris nisi ut aliquip ex ea commodo consequat. }
\showframe
\starttext
%\dorecurse{32}{ ~ \par }
%\dorecurse{33}{ ~ \par }
\dorecurse{34}{ ~ \par }
The following items are blah blah blsh:
\startitemize
\sym{-} \Lorem
\sym{-} \Lorem
\sym{-} \Lorem
\sym{-} \Lorem
\stopitemize
\stoptext
I find that \dorecurse{32} fits two items on the bottom of the first page and two at the top of the next. This is fine.
With \dorecurse{33} I get one and three - which is also fine.
With \dorecurse{34} all of the items move to the second page even though only one extra line has been added and there is now quite a large gap at the bottom of the first page.
Is there a setting that controls this a bit more precisely, please? (So that \dorecurse{34} and possibly even 35 would still split one and three.)
--
Bruce Horrocks
Hampshire, UK
___________________________________________________________________________________
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:[~2020-11-26 21:11 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-11-26 21:11 Bruce Horrocks [this message]
2020-11-26 21:41 ` Marco Patzer
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=DD7B6251-0C04-4D64-8F58-6E05C10DB92D@scorecrow.com \
--to=ntg@scorecrow.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).