From: Taco Hoekwater <taco@elvenkind.com>
Subject: Re: itemize[loose]
Date: Fri, 27 Jan 2006 08:46:41 +0100 [thread overview]
Message-ID: <43D9CFE1.9000109@elvenkind.com> (raw)
In-Reply-To: <1AD54492-2470-42CD-AEF0-A33F8AF5D9F2@science.uva.nl>
Hans van der Meer wrote:
> Error message:
> ! Undefined control sequence.
> <argument> \optimizeitemsfalse
>
> \p!compareprocessaction ...commalistelement {#3}#2
> \expandafter
> \quitcommalis...
> etc.
>
> Is this expected behaviour? The manual does not give me an idea about
> that.
No, the internal macro \dododosetupitemgroupconstant has bug.
The loose line has to be:
\v!loose*=>\setfalse\optimizelistitem,
instead of
\v!loose*=>\optimizeitemsfalse,
But it would not have helped for you underfull hbox messages,
loose is about vertical (pagebreak) optimizations. Your best bet
is \setuptolerance[stretch,verytolerant]
Cheers, taco
next prev parent reply other threads:[~2006-01-27 7:46 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-01-26 20:15 itemize[loose] Hans van der Meer
2006-01-27 7:46 ` Taco Hoekwater [this message]
2006-01-27 9:03 ` itemize[loose] Hans Hagen
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=43D9CFE1.9000109@elvenkind.com \
--to=taco@elvenkind.com \
--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).