From: Rik Kabel via ntg-context <ntg-context@ntg.nl>
To: ntg-context@ntg.nl
Cc: Rik Kabel <ConTeXt@rik.users.panix.com>
Subject: Re: No pagebreak before chapter
Date: Thu, 23 Dec 2021 15:31:41 -0500 [thread overview]
Message-ID: <a090e901-603b-6545-4284-ea63fe105bad@rik.users.panix.com> (raw)
In-Reply-To: <eba5bbf3d73768ad8d8bc3abd516be18a76a4b7b.camel@mailbox.org>
On 2021-12-23 14:15, juh via ntg-context wrote:
> Dear all,
>
> if I don't want pagebreaks before a chapter, I can do this:
>
> \setuphead
> [chapter,title]
> [style=\tfb,
> align=center,
> number=no,
> after=,
> page=no,
> sectionsegments=chapter,
> header=empty]
>
>
> In my project this does not work. All chapters start on a new page.
>
> What can I do to debug my code?
>
> I search for "page=" or "pagebreak" but found no configuration that can
> cause chapters to insert a pagebreak before.
>
> Merry Chrismas to all of you!
> juh
>
Pagebreak before chapter heading is the default behavior, so you are not
likely to find an explicit instance of it being set.
Do the other settings in your \setuphead come through (align, style,
number? What is the scope of the \setuphead command -- is it restricted
to a particular section block (frontpart, bodypart, backpart, appendix)?
Is this command overridden by a later \setuphead command within the same
scope?
--
Rik
___________________________________________________________________________________
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://context.aanhet.net
archive : https://bitbucket.org/phg/context-mirror/commits/
wiki : http://contextgarden.net
___________________________________________________________________________________
prev parent reply other threads:[~2021-12-23 20:31 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-12-23 19:15 juh via ntg-context
2021-12-23 20:31 ` Rik Kabel via ntg-context [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=a090e901-603b-6545-4284-ea63fe105bad@rik.users.panix.com \
--to=ntg-context@ntg.nl \
--cc=ConTeXt@rik.users.panix.com \
/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).