ntg-context - mailing list for ConTeXt users
 help / color / mirror / Atom feed
From: Hans Hagen <pragma@wxs.nl>
Subject: Re: Can itemize calculate optimal label widths?
Date: Mon, 23 Feb 2004 00:18:21 +0100	[thread overview]
Message-ID: <6.0.1.1.2.20040223001605.01dbf0d8@localhost> (raw)
In-Reply-To: <c14jgc$mj$1@sea.gmane.org>

At 10:18 20/02/2004, you wrote:
>Hi all!
>
>Is there a possiblity to have itemize calculate the optimal label width 
>itself? I have an itemize that has rather different labels, e.g.:
>
>\startitemize
>\sym{1.} An item
>\sym{2.} Another item
>\sym{103 a.} An item with a very broad label
>\stopitemize
>
>In this example the label "103 a." flows into the item text. It would be 
>great if itemize would automatically use a label width that fits the 
>broadest label.

for the moment use:

   \startitemize[2*broad]

and remind me in a few couple of weeks (months); it's on my mental to-do 
list (not that hard to implement probably)

Hans  

  reply	other threads:[~2004-02-22 23:18 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-02-20  9:18 Stefan Wachter
2004-02-22 23:18 ` Hans Hagen [this message]
2004-02-26 15:22   ` Stefan Wachter

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.1.1.2.20040223001605.01dbf0d8@localhost \
    --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).