From: Wolfgang Schuster <schuster.wolfgang@googlemail.com>
To: Kip Warner <kip@thevertigo.com>
Cc: mailing list for ConTeXt users <ntg-context@ntg.nl>,
"General discussion of LuaTeX." <luatex@tug.org>
Subject: Re: Itemize without page break
Date: Tue, 20 Mar 2012 06:22:43 +0100 [thread overview]
Message-ID: <7448136C-5F9E-44D5-8D5E-DF40EA6C3E57@googlemail.com> (raw)
In-Reply-To: <1332205456.3358.248.camel@kip-laptop>
Am 20.03.2012 um 02:04 schrieb Kip Warner:
> On Mon, 2012-03-19 at 09:17 +0100, Wolfgang Schuster wrote:
>> Make a example because this works:
>>
>> \starttext
>>
>> %\dorecurse{2}{\input tufte\par}
>> \dorecurse{3}{\input tufte\par}
>>
>> \startitemize[before={\startlinecorrection[blank]},after=
>> \stoplinecorrection]
>> \dorecurse{4}{\startitem \input ward \stopitem}
>> \stopitemize
>>
>> \dorecurse{3}{\input tufte\par}
>>
>> \stoptext
>
> I concur that your example works. Attached is an example of a minimal
> that does not for me. ConTeXt does its thing, invoking luatex which
> quickly gets nasty and starts spinning the clock - endlessly allocating
> memory until a 4GB system is run into the ground.
The problem is the empty second argument.
\startitemize[before=\startlinecorrection,after=\stoplinecorrection][]
When you pass two arguments with \startitemize the first argument os for keywords (e.g. packed or fit)
and second argument is for assignments (e.g. width=3cm) in your case context is looking for the keywords
“before=\startlinecorrection” and “after=\stoplinecorrection” which results in a loop.
Wolfgang
___________________________________________________________________________________
If your question is of interest to others as well, please add an entry to the Wiki!
maillist : ntg-context@ntg.nl / http://www.ntg.nl/mailman/listinfo/ntg-context
webpage : http://www.pragma-ade.nl / http://tex.aanhet.net
archive : http://foundry.supelec.fr/projects/contextrev/
wiki : http://contextgarden.net
___________________________________________________________________________________
next prev parent reply other threads:[~2012-03-20 5:22 UTC|newest]
Thread overview: 45+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-03-17 1:47 Kip Warner
2012-03-17 9:21 ` luigi scarso
2012-03-17 10:21 ` Wolfgang Schuster
2012-03-18 23:25 ` Kip Warner
2012-03-18 23:29 ` Kip Warner
2012-03-19 8:17 ` Wolfgang Schuster
2012-03-20 1:04 ` Kip Warner
2012-03-20 5:22 ` Wolfgang Schuster [this message]
2012-03-20 5:31 ` Kip Warner
2012-03-20 5:46 ` Wolfgang Schuster
2012-03-20 5:49 ` Kip Warner
2012-03-20 7:21 ` [luatex] " Patrick Gundlach
2012-03-20 15:02 ` Khaled Hosny
2012-03-20 8:17 ` Hans Hagen
2012-03-20 10:05 ` luigi scarso
2012-03-20 18:50 ` Kip Warner
2012-03-20 14:57 ` [luatex] " Khaled Hosny
2012-03-20 18:59 ` Kip Warner
2012-03-20 19:26 ` Hans Hagen
2012-03-20 19:59 ` Kip Warner
2012-03-20 20:39 ` luigi scarso
2012-03-20 21:24 ` Kip Warner
2012-03-20 21:41 ` luigi scarso
2012-03-22 1:50 ` Kip Warner
2012-03-20 20:44 ` Hans Hagen
2012-03-20 21:26 ` Kip Warner
2012-03-20 22:18 ` Kip Warner
2012-03-20 22:22 ` Aditya Mahajan
2012-03-22 2:01 ` Kip Warner
2012-03-22 10:38 ` Mojca Miklavec
2012-03-22 10:48 ` Hans Hagen
2012-03-22 10:48 ` Hans Hagen
2012-03-22 11:21 ` Philipp Gesang
2012-03-22 11:58 ` Philipp Gesang
2012-03-22 22:47 ` Kip Warner
2012-03-22 22:46 ` Kip Warner
2012-03-22 22:40 ` Kip Warner
2012-03-22 12:05 ` luigi scarso
2012-03-22 16:38 ` luigi scarso
2012-03-19 21:49 ` Hans Hagen
2012-03-20 0:43 ` Kip Warner
2012-03-20 8:11 ` Hans Hagen
2012-03-18 23:33 ` luigi scarso
2012-03-19 21:50 ` Hans Hagen
2012-03-20 0:41 ` Kip Warner
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=7448136C-5F9E-44D5-8D5E-DF40EA6C3E57@googlemail.com \
--to=schuster.wolfgang@googlemail.com \
--cc=kip@thevertigo.com \
--cc=luatex@tug.org \
--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).