ntg-context - mailing list for ConTeXt users
 help / color / mirror / Atom feed
From: Hans Hagen <pragma@wxs.nl>
Cc: "'ntg-context@ntg.nl'" <ntg-context@ntg.nl>
Subject: Re: White space between *items* in \startopsomming
Date: Tue, 07 Jul 1998 09:36:55 +0200	[thread overview]
Message-ID: <35A1D017.DB1FA1DD@wxs.nl> (raw)

Berend de Boer wrote:

> How can I influence white space between items (\som) within \startopsomming..\stopopsomming?
> 
> It seems that the white space settings influence parskip. I only want some space before every \som, but not within som's paragraph's. How?

This is exactly why we started writing context! We needed lots of
itemizations. So you can bet that much is supported

\stelopsommingin[elk][opelkaar,autointro] 

(or in english: \setupitemize[each][packed,autointro])

\startopsomming
\som eerste
\som tweede
\stopopsomming

You can also directly say:

\startopsomming[opelkaar]

With elk/each you tell context to apply this at each level (you can set
the maximum level if needed, currently 6). 

The autointro is another example of a switch. It keeps one liners to the
list, so yuou don't end up with 

bla bla bla: 
<next page> 
- first
- second

There are many tricks in itemizations, like: 

\startopsomming[breedte=8em,afstand=2em,items=4]
\its Ik kan \TeX\ niet missen.
\its Ik zal altijd \TeX\ blijven gebruiken.
\its Ik verwacht binnen enkele jaren een redelijk alternatief.
\its Ik gebruik naast \TeX\ ook andere zet|/|opmaakpakketten.
\its Ik gebruik \TeX\ nauwelijks.
\its Ik ben op zoek naar een ander systeem.
\stopopsomming

As said, opsommingen are among the oldest constructs in context. Now one
should watch out for another feature: 

**** itemizations are optimized in a second pass ****

This means that when you have large ones and add one more item or add a
whole new itemization, the rest can come out breaked wrong, but the next
pass is ok. ConTeXt keeps the first two and last two (or all three)
lines together (that is, when you use [packed] of course). 

There are some more two pass optimizations, guess where ...

Hans 

Hans 

-----------------------------------------------------------------
                                              Hans Hagen | PRAGMA
              Ridderstraat 27 | 8061 GH Hasselt | The Netherlands
    tel: 038 477 53 69 | fax: 038 477 53 74 | mail: pragma@wxs.nl
-----------------------------------------------------------------


             reply	other threads:[~1998-07-07  7:36 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
1998-07-07  7:36 Hans Hagen [this message]
  -- strict thread matches above, loose matches on Subject: below --
1998-07-06 18:15 Berend de Boer

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=35A1D017.DB1FA1DD@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).