From: Patrick Gundlach <pg@levana.de>
Subject: Re: Pagebreaks
Date: Sat, 27 Sep 2003 08:34:05 +0200 [thread overview]
Message-ID: <m23ceig2oy.fsf@levana.de> (raw)
In-Reply-To: <3E770E86-F03F-11D7-B0B7-00039318D414@uni-bonn.de> (Thomas A. Schmitz's message of "Fri, 26 Sep 2003 18:34:05 +0200")
"Thomas A.Schmitz" <thomas.schmitz@uni-bonn.de> writes:
> Thanks! This command alleviated the problem without eliminating all
> the "shorter" pages. \setuplayout[grid=yes] actually made it a lot
> worse; almost every page was several lines short. I suspect it might
> have something to with itemizations (of which there are quite a few);
> this seems to confuse (Con)TeX(t).
If you really want your problem solved, you should post an example.
Patrick
--
Why is it so difficult to post a minimal but complete example????
next prev parent reply other threads:[~2003-09-27 6:34 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-09-26 8:42 Pagebreaks Thomas A.Schmitz
2003-09-26 16:15 ` Pagebreaks Hans Hagen
2003-09-26 16:34 ` Pagebreaks Thomas A.Schmitz
2003-09-27 6:34 ` Patrick Gundlach [this message]
2003-09-27 7:48 ` Pagebreaks Thomas A.Schmitz
2003-09-27 18:20 ` Pagebreaks Patrick Gundlach
2003-09-28 20:22 Pagebreaks Thomas A.Schmitz
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=m23ceig2oy.fsf@levana.de \
--to=pg@levana.de \
--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).