From: Pablo Rodriguez <oinos@gmx.es>
To: mailing list for ConTeXt users <ntg-context@ntg.nl>
Subject: bug in \setupitemize?
Date: Thu, 11 Dec 2014 19:04:20 +0100 [thread overview]
Message-ID: <5489DCA4.9060002@gmx.es> (raw)
Dear list,
I have the following sample:
\showframe\showgrid
\setuppapersize[A6]
\setupitemize[inbetween={\blank[preference,big]}]
\starttext
\dorecurse{3}{\dorecurse{3}{Sometimes is really hard
to place list items. Am I missing something? }\par}
\startitemize
\item \dorecurse{5}{First item that I try. }
\item \dorecurse{15}{Second item that I write. }
\item \dorecurse{5}{Third item that I forgot. }
\stopitemize
\stoptext
Although I ask ConTeXt to try to insert a page break between list items
(which for some strange reason is avoided), the whole first list item is
moved to the next page, leaving a huge blank space in the previous page
(where the first list item would completely).
I have found this before and this is causing me problems when using lists.
Isn’t this a bug? (If not moving a whole first item to the next page
when it fits in the previous one, not obeying
inbetween={\blank[preference,big]} should be a bug.)
Or am I missing something?
Many thanks for your help,
Pablo
--
http://www.ousia.tk
___________________________________________________________________________________
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:[~2014-12-11 18:04 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-12-11 18:04 Pablo Rodriguez [this message]
2014-12-12 8:36 ` Hans Hagen
2014-12-12 15:32 ` Pablo Rodriguez
2014-12-12 17:53 ` Wolfgang Schuster
2014-12-12 18:39 ` 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=5489DCA4.9060002@gmx.es \
--to=oinos@gmx.es \
--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).