From: Hans Hagen <pragma@wxs.nl>
Cc: Unicode-based TeX for Mac OS X <xetex@tug.org>
Subject: Re: Re: [XeTeX] XeTeX infinite loop [][][][][][] bug - possible fix
Date: Thu, 16 Dec 2004 18:15:59 +0100 [thread overview]
Message-ID: <41C1C2CF.5050409@wxs.nl> (raw)
In-Reply-To: <20041216165605.3933@news.comp.lancs.ac.uk>
Adam Lindsay wrote:
> (That's a pretty harsh workaround, considering "extra_mem_bot.context =
> 4000000" is the default in gwTeX. ConTeXters may prefer the \hfuzz
> suggestion from the XeTeX list. In any case, it explains why I was seeing
> the infinite loop so early!)
one can always enlarge the main memory
Hans
-----------------------------------------------------------------
Hans Hagen | PRAGMA ADE
Ridderstraat 27 | 8061 GH Hasselt | The Netherlands
tel: 038 477 53 69 | fax: 038 477 53 74 | www.pragma-ade.com
| www.pragma-pod.nl
-----------------------------------------------------------------
prev parent reply other threads:[~2004-12-16 17:15 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <C9FE3A99-4F7F-11D9-8D8D-000393BD674C@sil.org>
2004-12-16 16:56 ` Adam Lindsay
2004-12-16 17:09 ` Jonathan Kew
2004-12-17 10:20 ` Adam Lindsay
2004-12-16 17:15 ` Hans Hagen [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=41C1C2CF.5050409@wxs.nl \
--to=pragma@wxs.nl \
--cc=ntg-context@ntg.nl \
--cc=xetex@tug.org \
/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).