From: Hans Hagen <pragma@wxs.nl>
Subject: Re: Re: itemize
Date: Wed, 28 Jul 2004 14:47:45 +0200 [thread overview]
Message-ID: <4107A071.9010302@wxs.nl> (raw)
In-Reply-To: <40D706A5.8030809@iname.com>
Gary Pajer wrote:
> Thomas A. Schmitz wrote:
>
>> Me stupid! Willi, this message made my day. I've been using ConTeXt
>> for more than a year now, but I was never able to figure out what
>> setupitemize [.1.] .1. number each meant. So it's the level of
>> itemization. Thanks, that should make things easier. And many thanks
>> to Patrick and to you for pointing out the left= option. ConTeXt and
>> the number of options it gives never cease to amaze me!
>
>
> since we're back on the topic of itemize, I'll repost a question that
> I've posted here before:
>
> -----------------------------------------------------
>
> It seems to me that the 'before' and 'after' keywords used in the third
> argument of \setupitemize are operative only if 'columns' are also
> specified. In the example below, the hairlines disappear if the
> 'columns'
> keyword is eliminated.
>
>
> Feature, bug, or misunderstanding?
a bit of all, this will take me some time (maybe when i redo the item
environment); has to do with grouping and such as well as before/after
handling
(compare output with\chardef\autoitemgroupspacing=0 set)
>
> BTW: can the lengths of the two hairlines in this example be made to be
> the same length? What's causing the indentation of the first hairline?
a bit tricky: par's (\endgraf's interfere in such matters, i.e. you need
to invoke the command when the width is (still) known)
\setupitemize
[2]
[a,packed,columns]
[before={\thinrule\endgraf},
after={\endgraf\thinrule}]
prev parent reply other threads:[~2004-07-28 12:47 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-06-16 15:12 itemize, adobekb Thomas A.Schmitz
2004-06-18 17:03 ` itemize Patrick Gundlach
2004-06-19 17:14 ` itemize Willi Egger
2004-06-20 7:57 ` itemize Patrick Gundlach
2004-06-20 20:41 ` itemize Willi Egger
2004-06-21 8:39 ` Thomas A. Schmitz
2004-06-21 16:02 ` Gary Pajer
2004-07-28 12:47 ` Hans Hagen [this message]
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=4107A071.9010302@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).