From: Hans Hagen <pragma@wxs.nl>
Subject: Re: The whole (sub)section on a single page
Date: Mon, 14 Nov 2005 20:39:36 +0100 [thread overview]
Message-ID: <4378E7F8.4000505@wxs.nl> (raw)
In-Reply-To: <6faad9f00511141011g40a31af8nac87df252a3d6f5e@mail.gmail.com>
Mojca Miklavec wrote:
>Taco Hoekwater wrote:
>
>
>>Mojca Miklavec wrote:
>>
>>
>>>It doesn't need to automatically determine the subsection boundaries
>>>automatically (although this would be great), so I can write something
>>>like this:
>>>
>>>\startmaterialforonepage
>>>\subsection{split only if too long for one page}
>>>\dorecurse{10}{whatever comes here \dots }
>>>\stopmaterialforonepage
>>>
>>>
>>Do you want something like this?
>>
>> \long\def\startmaterialforonepage#1\stopmaterialforonepage%
>> {\setbox0\vbox{#1}\ifdim\ht0<\textheight \page\fi #1}
>>
>>
>
>Thak you, Taco. Yes, this is almost exactly what I wanted to do,
>except that I would substitute
> \ifdim\ht0<\textheight
>with
> \ifdim\ht0<\theremainingpageheight
>
>How/where can I get \theremainingpageheight? I saw some strange
>"keywords" like \pagegoal, \pagetotal spread through the source, ...
>but I have no clue what they are for and if they have anyting to do
>with what I'm looking for.
>
>
that's always tricky, because it's not really possible to determine the
rest of the available space without entering the output routing, which
then spoils spacing
(there is \testpage[n] with n being a minimal number of lines, so,
\testpage[10] will move to the next page if there are less than 10 lines)
Hans
next prev parent reply other threads:[~2005-11-14 19:39 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-11-12 23:55 Mojca Miklavec
2005-11-13 13:58 ` Taco Hoekwater
2005-11-14 18:11 ` Mojca Miklavec
2005-11-14 19:39 ` Hans Hagen [this message]
2005-11-15 8:15 ` Mojca Miklavec
2005-11-15 9:38 ` Hans Hagen
2005-12-01 8:35 ` Christopher Creutzig
2005-12-01 9:29 ` Hans Hagen
2005-12-06 22:00 ` Christopher Creutzig
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=4378E7F8.4000505@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).