ntg-context - mailing list for ConTeXt users
 help / color / mirror / Atom feed
From: Hans Hagen <pragma@wxs.nl>
Cc: ntg-context@ntg.nl
Subject: Re: Problem with \nobreak
Date: Fri, 20 Oct 2000 09:37:43 +0200	[thread overview]
Message-ID: <3.0.6.32.20001020093743.018eeb60@pop.wxs.nl> (raw)
In-Reply-To: <20001019193429.A47271@prioris.mini.pw.edu.pl>

At 07:34 PM 10/19/00 +0200, Slawek Zak wrote:
>On Thu, Oct 19, 2000 at 06:25:09PM +0200, Hans Hagen wrote:
>> At 06:15 PM 10/19/00 +0200, Slawek Zak wrote:
>> >On Thu, Oct 19, 2000 at 11:12:37AM +0200, Hans Hagen wrote:
>> >> >\definehead[Section][subject]
>> >> >\setuphead[Section][style=cap,textcommand=\underbar]
>> >> 
>> >> this is ok. 
>> >
>> >Well... it is not, as I have one `Section' that has title at the
>> >bottom of a page.
>> 
>> Then maybe the first command after that is goodbreaking? What is the first
>> command after the section header? 
>
>It's \startitemize and then \item's 

I guessed so, since that command prefers a new page. Actually itemize will
also prevent a break between the first two and last two items [second pass
optimization]. 

You may try: 

\startitemize[intro]

which will as good as possible prevent a break (or \page[no])

Hans
-------------------------------------------------------------------------
                                                  Hans Hagen | PRAGMA ADE
                      Ridderstraat 27 | 8061 GH Hasselt | The Netherlands
 tel: +31 (0)38 477 53 69 | fax: +31 (0)38 477 53 74 | www.pragma-ade.com
-------------------------------------------------------------------------


  reply	other threads:[~2000-10-20  7:37 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2000-10-17 20:06 Slawek Zak
2000-10-17 21:35 ` Hans Hagen
2000-10-18 16:51   ` Slawek Zak
2000-10-19  9:12     ` Hans Hagen
2000-10-19 16:15       ` Slawek Zak
2000-10-19 16:25         ` Hans Hagen
2000-10-19 17:34           ` Slawek Zak
2000-10-20  7:37             ` Hans Hagen [this message]
2000-10-22 22:26               ` Slawek Zak
2000-10-19 16:26         ` Hans Hagen

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=3.0.6.32.20001020093743.018eeb60@pop.wxs.nl \
    --to=pragma@wxs.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).