From: Willi Egger <w.egger@boede.nl>
Subject: Re: another itemize question
Date: Wed, 29 Oct 2003 09:49:17 +0100 [thread overview]
Message-ID: <6.0.0.22.1.20031029094411.01b1b870@digitpaint.nl> (raw)
In-Reply-To: <002d01c39d57$801dfb70$01fd5644@playroom>
Hi,
Triggered by your question I tried the code. Indeed also here with Context
version:
ConTeXt ver: 2003.9.25 fmt: 2003.9.25 int: english mes: english
the described behaviour occurs. - I tried to look things up in TeXshow, but
unfortunately the \setupitemize command is not listed there. - In the
english manual I could find the use of this command, still wasn't able to
get the puzzle solved....
Sorry can't help you in this.
Willi
At 14:29 28.10.2003, Gary wrote:
>I continue to have problems understanding itemize.
>
>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?
>
>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?
>
>Regards,
>Gary
>
>----------------------------------------------------------------------------
>---------
>
>\setupitemize[2][a,packed,columns][before={\hairline},after={\hairline}]
>\setupitemize[1][n]
>
>\starttext
>\startitemize
>%
>\item Level One
>%
>\startitemize
>\item first
>\item second
>\item third
>\stopitemize
>%
>\item Forgot a level
>%
>\startitemize
>\item one
>\item two
>\item three
>\stopitemize
>%
>\item Level two
>%
>\startitemize
>\item here's one
>\item here's another
>\item finally this
>\stopitemize
>%
>\stopitemize
>%
>\stoptext
>
>_______________________________________________
>ntg-context mailing list
>ntg-context@ntg.nl
>http://www.ntg.nl/mailman/listinfo/ntg-context
next prev parent reply other threads:[~2003-10-29 8:49 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-10-09 4:27 \index + \definedescription Pavel Stupin
2003-10-09 7:47 ` Willi Egger
2003-10-10 7:15 ` Pavel Stupin
2003-10-10 18:19 ` Willi Egger
2003-10-12 3:48 ` itemize: before/after only with columns? Gary Pajer
2003-10-28 13:29 ` another itemize question Gary Pajer
2003-10-29 8:49 ` Willi Egger [this message]
2003-10-29 22:57 ` Patrick Gundlach
2003-10-30 2:41 ` Gary Pajer
2003-10-30 15:48 ` Patrick Gundlach
2003-10-31 3:44 ` Gary Pajer
2003-10-31 8:34 ` Patrick Gundlach
2003-10-30 2:48 ` Gary Pajer
2003-10-30 2:54 ` Gary Pajer
2004-04-16 18:50 ` Baffling error Paulo Ney de Souza
2004-04-16 19:24 ` Willi Egger
2004-04-16 19:29 ` Paulo Ney de Souza
2004-04-16 19:51 ` Willi Egger
2004-04-16 19:56 ` Paulo Ney de Souza
2004-04-16 20:10 ` Willi Egger
2004-04-16 20:18 ` Paulo Ney de Souza
2004-04-16 20:36 ` Willi Egger
2004-04-17 11:44 ` George N. White III
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=6.0.0.22.1.20031029094411.01b1b870@digitpaint.nl \
--to=w.egger@boede.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).