ntg-context - mailing list for ConTeXt users
 help / color / mirror / Atom feed
From: Alan Bowen <bowenalan03@gmail.com>
To: mailing list for ConTeXt users <ntg-context@ntg.nl>
Subject: Re: preventing page breaks after headings
Date: Tue, 12 Jun 2012 08:17:09 -0400	[thread overview]
Message-ID: <CAFMOkGWhWxDNO5jKWgm7O864JkT4U22bs8cO4h3bd=MAo_hCbw@mail.gmail.com> (raw)
In-Reply-To: <BBB2076E-599E-4266-A97E-014F28BC6374@googlemail.com>


[-- Attachment #1.1: Type: text/plain, Size: 1847 bytes --]

Thanks!, Wolfgang. As ever, you are a life saver. I was able to remove all
but one of the weird page breaks using your suggestions. The last one was
resolved by moving a \startegister a few words further along in the
paragraph.

Alan

On Sun, Jun 10, 2012 at 3:13 PM, Wolfgang Schuster <
schuster.wolfgang@googlemail.com> wrote:

>
> Am 10.06.2012 um 20:52 schrieb Alan Bowen:
>
> > Is there a way in MKII to ensure that there is never a page break
> between a heading and the following text?
> >
> > \setuphead[after={\page[no]}] does not seem to work without entering
> vertical mode before \page. But, so far, I have not found a way to enter
> vertical mode in after={…} that does not add interlinespace and thus place
> the text too far from the heading.
> >
> > Any suggestion or alternatives?
>
> Do you have a example where you get an unwanted page break because context
> tries to prevent it.
>
> When you can’t make one in a short time try one of the following methods:
>
>
> 1. Insert a page break before the heading when not enough space is
> available.
>
> \setuphead[…][before={\testpage[6]\blank[…]}]
>
>
> 2. Add a big penalty before the vertical space after the heading (don’t
> use this method in mkiv).
>
> \setuphead[…][after={\nobreak\blank[…]}]
>
>
> Wolfgang
>
> ___________________________________________________________________________________
> 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
>
> ___________________________________________________________________________________
>

[-- Attachment #1.2: Type: text/html, Size: 2561 bytes --]

[-- Attachment #2: Type: text/plain, Size: 485 bytes --]

___________________________________________________________________________________
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
___________________________________________________________________________________

      reply	other threads:[~2012-06-12 12:17 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-06-10 18:52 Alan Bowen
2012-06-10 19:13 ` Wolfgang Schuster
2012-06-12 12:17   ` Alan Bowen [this message]

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='CAFMOkGWhWxDNO5jKWgm7O864JkT4U22bs8cO4h3bd=MAo_hCbw@mail.gmail.com' \
    --to=bowenalan03@gmail.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).