From: Andreas Harder <aharder@uni-koblenz.de>
To: mailing list for ConTeXt users <ntg-context@ntg.nl>
Subject: Re: prevent page break after head
Date: Wed, 29 Sep 2010 10:42:21 +0200 [thread overview]
Message-ID: <5EB13A2F-AFC4-40CA-8B8F-CA5CAAAA94B0@uni-koblenz.de> (raw)
In-Reply-To: <3A893DF9-0269-410D-BE34-5E0BCC6C0E57@st.estfiles.de>
Am 29.09.2010 um 10:29 schrieb Steffen Wolfrum:
>
> Am 29.09.2010 um 10:21 schrieb Andreas Harder:
>
>> Hi all,
>>
>> please have a look at the following example:
>>
>> \starttext \showframe
>> \section{test}
>> \dorecurse{36}{test\par}
>> \section{test}
>> \startitemize
>> \dorecurse{12}{\item #1}
>> \stopitemize
>> % \dorecurse{12}{• #1\blank}
>> \stoptext
>>
>> I would like to prevent the page break after the second section. It works okay if the head is followed by normal text.
>>
>> Is there a key I have not found yet? I tried all kind of combinations …
>
>
> Just add a \testpage[4] before the second \section{test}
Thank you! This works. So I will try \setuphead[section][before={\testpage[4]\blank[2*big]}]. But I'm curious, why do it work with normal text?
\starttext \showframe
\section{test}
\dorecurse{36}{test\par}
\section{test}
\dorecurse{12}{• #1\blank}
\stoptext
Andreas
___________________________________________________________________________________
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 prev parent reply other threads:[~2010-09-29 8:42 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-09-29 8:21 Andreas Harder
2010-09-29 8:29 ` Steffen Wolfrum
2010-09-29 8:42 ` Andreas Harder [this message]
2010-09-29 11:22 ` Wolfgang Schuster
2010-09-29 12:24 ` Andreas Harder
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=5EB13A2F-AFC4-40CA-8B8F-CA5CAAAA94B0@uni-koblenz.de \
--to=aharder@uni-koblenz.de \
--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).