ntg-context - mailing list for ConTeXt users
 help / color / mirror / Atom feed
From: Slawek Zak <zaks@prioris.mini.pw.edu.pl>
Subject: Re: Problem with \nobreak
Date: Wed, 18 Oct 2000 18:51:58 +0200	[thread overview]
Message-ID: <20001018185158.C42784@prioris.mini.pw.edu.pl> (raw)
In-Reply-To: <3.0.6.32.20001017233529.01487800@pop.wxs.nl>

On Tue, Oct 17, 2000 at 11:35:29PM +0200, Hans Hagen wrote:
> At 10:06 PM 10/17/00 +0200, Slawek Zak wrote:
> >I tried to define my own sectioning command, like this:
> >
> >  \setuphead[Section][style=cap,textcommand=\underbar,after=\nobreak]
> >
> >I don't know why, but after one of so defined `Sections' the page is
> >broken. Can I somehow prevent this?
> 
> \setuphead[Section][section][....]

Hmm. The above doesn't work. It's not mentioned in the manual, the
english one, that \setuphead has 3 arguments and it seems not to have
3.

Full definition of Section is now:

\definehead[Section][subject]
\setuphead[Section][style=cap,textcommand=\underbar]

I use subject to avoid numbering (it's the same as section in other
respects, right?), and to have subpages. If I change subject to
section it's still the same (but the numbers of course).

> you need a parent sectioning id, and: no \nobeak! ! ! since context already
> uses a weighted system of not breaking after headers [so that successive
> ones all move to the next page]

Great to hear that. Is the 3-argument setuphead available only in
beta?

/S


  reply	other threads:[~2000-10-18 16:51 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 [this message]
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
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=20001018185158.C42784@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).