From: Taco Hoekwater <taco@elvenkind.com>
Subject: Re: vertical stretch problem
Date: Sun, 08 Jan 2006 11:54:53 +0100 [thread overview]
Message-ID: <43C0EF7D.6050301@elvenkind.com> (raw)
In-Reply-To: <Pine.LNX.4.58.0601071742350.4658@gaston.free.fr>
Peter Münster wrote:
> Hello,
> please consider the following example:
>
> \setupalign[line]% because I want something like "flush-bottom"
> \starttext
> \chapter{Anhang}
> \section{Sec1}
> \input tufte
>
> \placetable{bla}{\vbox to 18cm{bla}}
>
> \section{Sec2}
> \input tufte
> \stoptext
>
> Of course, vertical stretch is good, but not *after* the section titles,
> better would be *before*.
>
> How could I better distribute the stretch?
You can fix the sections by
\setupalign[line]
\setuphead[chapter][before={\hbox{}\blank[2*line]\vfill}]
\setuphead[section][before={\blank[2*line]\vfil}]
But I wouldn't call that a true solution. Better (perhaps) is:
\scratchskip 0pt plus 1 fill
\advance\topskip\scratchskip
Cheers, Taco
next prev parent reply other threads:[~2006-01-08 10:54 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-01-07 16:45 Peter Münster
2006-01-08 10:54 ` Taco Hoekwater [this message]
2006-01-08 19:12 ` Peter Münster
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=43C0EF7D.6050301@elvenkind.com \
--to=taco@elvenkind.com \
--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).