ntg-context - mailing list for ConTeXt users
 help / color / mirror / Atom feed
From: Willi Egger <w.egger@boede.nl>
To: mailing list for ConTeXt users <ntg-context@ntg.nl>
Subject: Re: Preventing page break
Date: Wed, 24 Jan 2007 20:52:51 +0100	[thread overview]
Message-ID: <45B7B913.2040201@boede.nl> (raw)
In-Reply-To: <200701240847.55281.mgb-debian@yosemite.net>

Hi Elliot,

humble, I agree with Mike's statement.
In general the \setuphead command is used to organize the behaviour of 
the section titles. By default only the \chapter and \part start on a 
right page in a doublesided layout.
See also cont-enp.pdf (The manual) on page 148 (text elements) section 
8.5 Alternative mechanisms.


Willi

Mike Bird wrote:
> On Wednesday 24 January 2007 08:21, Elliot Clifton wrote:
>   
>> Mike wrote:
>>     
>>> Does "\setuphead[chapter][before={\page[yes]}]" do what you want?
>>>       
>> No. I want to remove empty pages that are being auto generated at the
>> end of a section.
>>     
>
> Hi Elliot,
>
> I think you'll need to post the relevant part of your setup, as
> ConTeXt does not create empty pages after sections by default,
> even in double-sided documents:
>
> \starttext
> \setuppagenumbering[alternate=doublesided]
> \section{A}
> \section{B}
> \stoptext
>
> --Mike Bird
> _______________________________________________
> ntg-context mailing list
> ntg-context@ntg.nl
> http://www.ntg.nl/mailman/listinfo/ntg-context
>   

  reply	other threads:[~2007-01-24 19:52 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-01-24 16:21 Elliot Clifton
2007-01-24 16:47 ` Mike Bird
2007-01-24 19:52   ` Willi Egger [this message]
  -- strict thread matches above, loose matches on Subject: below --
2019-07-10 10:52 preventing " Floris van Manen
2019-07-19 11:24 ` Henning Hraban Ramm
2007-01-24 21:31 Preventing " Elliot Clifton
2007-01-24  0:25 Elliot Clifton
2007-01-24  0:56 ` Mike Bird

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=45B7B913.2040201@boede.nl \
    --to=w.egger@boede.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).