From: Hans Hagen <pragma@wxs.nl>
To: ConTeXt list <ntg-context@ntg.nl>
Subject: Re: new issue with page break
Date: Thu, 06 May 2010 16:37:50 +0200 [thread overview]
Message-ID: <4BE2D43E.6030605@wxs.nl> (raw)
In-Reply-To: <20100506123931.GA31555@gaston.couberia.bzh>
On 6-5-2010 2:39, Peter Münster wrote:
> Hello,
>
> IMHO there should never be a page break right *after* a section header, but
> here it is:
>
> \starttext
> \dorecurse{660}{text }
> \section{bla}
> % \par\page[no] % does not help
> \startTEX
> bla
> bla
> \stopTEX
> \stoptext
>
> My actual work-around: \page before \section{}
>
> Is there a better solution?
function buffers.verbatimbreak(n,m)
if flags.optimize_verbatim then
if n == 2 or n == m then
texsprint(no_break_command)
elseif n > 1 then
texsprint(do_break_command)
end
end
end
in buff-ini.lua or otherwise \optimizeverbatimfalse
-----------------------------------------------------------------
Hans Hagen | PRAGMA ADE
Ridderstraat 27 | 8061 GH Hasselt | The Netherlands
tel: 038 477 53 69 | voip: 087 875 68 74 | www.pragma-ade.com
| www.pragma-pod.nl
-----------------------------------------------------------------
___________________________________________________________________________________
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
___________________________________________________________________________________
prev parent reply other threads:[~2010-05-06 14:37 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-05-06 12:39 Peter Münster
2010-05-06 14:37 ` Hans Hagen [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=4BE2D43E.6030605@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).