ntg-context - mailing list for ConTeXt users
 help / color / mirror / Atom feed
From: "Lance Larsen" <lance.c.larsen@gmail.com>
To: <ntg-context@ntg.nl>
Subject: Re: Heading flow
Date: Wed, 1 May 2013 15:01:28 -0700	[thread overview]
Message-ID: <518190ba.e834440a.73c0.5cc1@mx.google.com> (raw)

Using the continue=no option of setuphead (in MKIV) didn't seem to work (not
sure why). What I did as a workaround was to a blank paragraph after each
heading (using 'after' in setuphead) and then packed the result. Not
necessarily an ideal solution, but adequate for what I needed.

\definehead[references][subsection]
\setuphead[references][after={ ~ }]

\startpacked   % Get rid of large gaps between the references.
\dorecurse{10}{\references{Reference item}}
\stoppacked

-Lance


Am 01.05.2013 um 18:03 schrieb Lance Larsen <lance.c.larsen at gmail.com>:

> It looks like the 'after' property of \setuphead can be used to override
the
> 'keep with next' behavior of the headings.

No, you need the continue key to disable this feature.

\setuphead[section][continue=no]

Wolfgang

___________________________________________________________________________________
If your question is of interest to others as well, please add an entry to the Wiki!

maillist : ntg-context@ntg.nl / http://www.ntg.nl/mailman/listinfo/ntg-context
webpage  : http://www.pragma-ade.nl / http://tex.aanhet.net
archive  : http://foundry.supelec.fr/projects/contextrev/
wiki     : http://contextgarden.net
___________________________________________________________________________________


             reply	other threads:[~2013-05-01 22:01 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-05-01 22:01 Lance Larsen [this message]
2013-05-01 22:20 ` Wolfgang Schuster
  -- strict thread matches above, loose matches on Subject: below --
2013-05-01 16:03 Lance Larsen
2013-05-01 20:26 ` Wolfgang Schuster
2013-05-01 13:37 lance.c.larsen

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=518190ba.e834440a.73c0.5cc1@mx.google.com \
    --to=lance.c.larsen@gmail.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).