From: Aditya Mahajan <adityam@umich.edu>
To: mailing list for ConTeXt users <ntg-context@ntg.nl>
Subject: Re: Serried itemized list with long items.
Date: Thu, 25 Jan 2007 19:51:38 -0500 (EST) [thread overview]
Message-ID: <alpine.WNT.0.81.0701251950380.764@nqvgln> (raw)
In-Reply-To: <200701251420.51246.john@wexfordpress.com>
On Thu, 25 Jan 2007, John R. Culleton wrote:
> I used \setupitemize[serried] for a numbered list. The items were each wider
> than the text block so they wrapped around to a second line. As a result
> Context left a blank line between items. I got
> 1. xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
> xxxxxxxxxxxxx
>
> 2. xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
> xxxxxxxxxxxxxxxxxxx
>
> ...which is not what I wanted :<(
Does \setupitemize[serried,joinedup,packed] help? (One of joinedup and
packed controls the spacing between items, I do not remember which)
Aditya
prev parent reply other threads:[~2007-01-26 0:51 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-01-25 19:20 John R. Culleton
2007-01-26 0:51 ` Aditya Mahajan [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=alpine.WNT.0.81.0701251950380.764@nqvgln \
--to=adityam@umich.edu \
--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).