ntg-context - mailing list for ConTeXt users
 help / color / mirror / Atom feed
From: Hans Hagen <pragma@wxs.nl>
To: mailing list for ConTeXt users <ntg-context@ntg.nl>
Subject: Re: How to properly `\setuplayout' for several pages and then restore back?
Date: Sun, 24 May 2015 11:20:17 +0200	[thread overview]
Message-ID: <556197D1.3030106@wxs.nl> (raw)
In-Reply-To: <CAKu-7WzvO4zj_Z5O7sYJPCqisrgM3BrzEEhKpg3WPSsrPdGNAA@mail.gmail.com>

On 5/23/2015 8:36 PM, Alexander Shukaev wrote:
> Hello,
>
> I have a table of contents that now has grown to span several pages.
> Before that I used the following setup:
>
> \definemakeup
> [contentspage]
>
> \setupmakeup
> [contentspage][%
>    footerstate={stop},
>    headerstate={stop},
>      pagestate={stop},
>           page={yes},
>         bottom={\vfill},
>            top={},
> ]
>
> \setuplayout
> [contentspage][%
>    footer={\zeropoint},
>    header={\zeropoint},
> ]
>
> \setuplayout
> [contentspage][%
>    footerdistance={\zeropoint},
>    headerdistance={\zeropoint},
> ]
>
> \startcontentspagemakeup
>
> \setupwhitespace
> [line]
>
> % ToC
>
> \stopcontentspagemakeup
>
> and that indeed worked when ToC spanned only one page.  Since page
> breaking does not work inside `makeup', I had ti give it up.  Now I try
> the following:
>
> \start
>
> \setupheader[state={stop}]
> \setupfooter[state={stop}]
>
> \setuppagenumbering[state={stop}]
>
> \setuplayout[%
>    footer={\zeropoint},
>    header={\zeropoint},
> ]
>
> \setuplayout[%
>    footerdistance={\zeropoint},
>    headerdistance={\zeropoint},
> ]
>
> % ToC
>
> \stop
>
> Why after `\stop' previous setups for `layout', `header', `footer', and
> `pagenumbering' do not restore?  Is there a way to achieve this or do I
> have to manually duplicate the setups which were before `\start'?  Thank
> you.

switching layouts is tricky as there is a mix between local and global 
settings and actions around the page crossing

\startlayout[name]

\stoplayout

also, when there is a layout defined with the same name as a makeup, 
then the makeup will take that layout

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

  reply	other threads:[~2015-05-24  9:20 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-05-23 18:36 Alexander Shukaev
2015-05-24  9:20 ` Hans Hagen [this message]
2015-05-24 17:53   ` Alexander Shukaev

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=556197D1.3030106@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).