From: Steffen Wolfrum <context@st.estfiles.de>
To: Taco Hoekwater <taco@elvenkind.com>
Cc: mailing list for ConTeXt users <ntg-context@ntg.nl>,
Hans Hagen <pragma@wxs.nl>
Subject: Re: luatex hangs at 100% cpu
Date: Wed, 17 Nov 2010 12:31:54 +0100 [thread overview]
Message-ID: <B4FFB506-F524-4493-92D2-210A7F42111A@st.estfiles.de> (raw)
In-Reply-To: <4CE3A1B7.9080601@elvenkind.com>
Am 17.11.2010 um 10:34 schrieb Taco Hoekwater:
> On 11/16/2010 12:59 PM, Steffen Wolfrum wrote:
>>
>> Hi,
>>
>> the current MkIV (ConTeXt ver: 2010.11.12) seems to have problems
>> with start/stopitemize and start/stopcolumns:
>>
>>
>> mostly it hangs at 100% cpu, sometimes it gives this error massage:
>
> We have had a case where luatex goes into a busy loop recently and that
> was caused by an undefined $HOME. Can you check and see if that is
> the problem?
MacBookPro:~ steffen$ echo $HOME
/Users/steffen
> Otherwise a test file is needed.
\setupstructure[state=start]
\starttext
\startitemize
\sym{one}test
\sym{two}test
%\sym{three}test % <- un/comment this
\stopitemize
\stoptext
Groeten,
Steffen
___________________________________________________________________________________
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:[~2010-11-17 11:31 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-11-16 11:59 Steffen Wolfrum
2010-11-17 9:34 ` Taco Hoekwater
2010-11-17 11:31 ` Steffen Wolfrum [this message]
2010-11-17 12:48 ` Taco Hoekwater
[not found] ` <85D758D2-104C-4A86-B79F-04472A5E0D05@st.estfiles.de>
2010-11-17 15:51 ` Hans Hagen
2010-11-17 15:57 ` Steffen Wolfrum
2010-11-17 12:54 ` Florian Wobbe
2010-11-17 14:11 ` 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=B4FFB506-F524-4493-92D2-210A7F42111A@st.estfiles.de \
--to=context@st.estfiles.de \
--cc=ntg-context@ntg.nl \
--cc=pragma@wxs.nl \
--cc=taco@elvenkind.com \
/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).