ntg-context - mailing list for ConTeXt users
 help / color / mirror / Atom feed
From: Aditya Mahajan <adityam@umich.edu>
To: mailing list for ConTeXt users <ntg-context@ntg.nl>
Subject: Re: Fwd: Re: Stray blank page with part
Date: Wed, 20 Dec 2017 12:40:36 -0500 (EST)	[thread overview]
Message-ID: <alpine.LNX.2.20.1712201239350.29440@ybpnyubfg.ybpnyqbznva> (raw)
In-Reply-To: <5e8304f0-80d8-bba0-d7ea-66c8c235b800@wxs.nl>

[-- Attachment #1: Type: text/plain, Size: 1961 bytes --]

On Wed, 20 Dec 2017, Hans Hagen wrote:
> -------- Forwarded Message --------
> Subject: Re: [NTG-context] Stray blank page with part
> Date: Wed, 20 Dec 2017 11:50:11 +0100
> From: Hans Hagen <pragma@wxs.nl>
> To: Henri <henrimenke@gmail.com>
>
> On 12/19/2017 9:15 PM, Henri wrote:
>>  Dear list,
>>
>>  Motivated by
>>  https://tex.stackexchange.com/questions/406892
>>  I wanted to disable page breaks for parts.  This works on all pages,
>>  except the first page of a
>>  document.  Why?  MWE is below as always.  Reproducible with TL 2017 and
>>  latest beta.
>>
>>  Cheers, Henri
>>
>>
>>
>>  \setuphead
>>     [part]
>>     [page=no]
>>
>>  \starttext
>>
>>  \startpart[title=Part One]
>>     \startchapter[title=Chapter One]
>>     \stopchapter
>>     \startchapter[title=Chapter Two]
>>     \stopchapter
>>  \stoppart
>>    \startpart[title=Part Two]
>>     \startchapter[title=Chapter One]
>>     \stopchapter
>>     \startchapter[title=Chapter Two]
>>     \stopchapter
>>  \stoppart
>>
>>  \stoptext
> this relates to the fatc that there has to be some node on the page that 
> registers the part information and as chapter flushes a page that one ends up 
> on a page then
>
> %  solution 1:
>
> \setuphead
>   [part]
>   [page=no,
>    placehead=hidden]
>
> \setuptexttexts
>   [\synchronizehead{part}]
>
> %  solution 2:
>
> \setuphead
>   [part]
>   [page=no,
>    placehead=hidden]
>
> \appendtoks
>    \synchronizehead{part}%
> \to \everybeforepagebody
>
> %  solution 3 (new in beta):
>
> \setuphead
>   [part]
>   [placehead=section]
>
> This will delay the flush till the next section head gets place. It's still 
> not 100% predictable but it might work out ok in most cases.

Another option, that I posted on Tex.se is:

\setuphead[chapter][continue=no]

So that the page is not flushed by \startchapter immediate after a 
\startpart.

Aditya

[-- Attachment #2: Type: text/plain, Size: 492 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://context.aanhet.net
archive  : https://bitbucket.org/phg/context-mirror/commits/
wiki     : http://contextgarden.net
___________________________________________________________________________________

  reply	other threads:[~2017-12-20 17:40 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <86d61f5f-371b-3a6b-dc9e-9796cccfa80f@wxs.nl>
2017-12-20 10:50 ` Hans Hagen
2017-12-20 17:40   ` Aditya Mahajan [this message]
2017-12-20 21:07     ` Hans Hagen
2017-12-20 17:44   ` Aditya Mahajan
2017-12-20 21:16     ` 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=alpine.LNX.2.20.1712201239350.29440@ybpnyubfg.ybpnyqbznva \
    --to=adityam@umich.edu \
    --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).