From: Slawek Zak <zaks@prioris.mini.pw.edu.pl>
Subject: Re: Problem with \nobreak
Date: Thu, 19 Oct 2000 19:34:29 +0200 [thread overview]
Message-ID: <20001019193429.A47271@prioris.mini.pw.edu.pl> (raw)
In-Reply-To: <3.0.6.32.20001019182509.01907920@pop.wxs.nl>
On Thu, Oct 19, 2000 at 06:25:09PM +0200, Hans Hagen wrote:
> At 06:15 PM 10/19/00 +0200, Slawek Zak wrote:
> >On Thu, Oct 19, 2000 at 11:12:37AM +0200, Hans Hagen wrote:
> >> >\definehead[Section][subject]
> >> >\setuphead[Section][style=cap,textcommand=\underbar]
> >>
> >> this is ok.
> >
> >Well... it is not, as I have one `Section' that has title at the
> >bottom of a page.
>
> Then maybe the first command after that is goodbreaking? What is the first
> command after the section header?
It's \startitemize and then \item's
/S
next prev parent reply other threads:[~2000-10-19 17:34 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-10-17 20:06 Slawek Zak
2000-10-17 21:35 ` Hans Hagen
2000-10-18 16:51 ` Slawek Zak
2000-10-19 9:12 ` Hans Hagen
2000-10-19 16:15 ` Slawek Zak
2000-10-19 16:25 ` Hans Hagen
2000-10-19 17:34 ` Slawek Zak [this message]
2000-10-20 7:37 ` Hans Hagen
2000-10-22 22:26 ` Slawek Zak
2000-10-19 16:26 ` Hans Hagen
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=20001019193429.A47271@prioris.mini.pw.edu.pl \
--to=zaks@prioris.mini.pw.edu.pl \
/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).