From: Matthew Baker <mbaker@mmkmail.gmd.de>
Subject: input stack size limit?
Date: Fri, 23 Apr 1999 10:31:10 +0200 [thread overview]
Message-ID: <Pine.SGI.4.04.9904231025350.48024-100000@sono> (raw)
Hi,
This is probably more a TeX question than a Context question but the
problem is coming up in Context, so....
I have been running Context under Linux without any problems for a while.
I've just tried getting it going on an SGI (IRIX 6.5). It is having
problems. Specifically, I get a
! TeX capacity exceeded, sorry [input stack size=1500].
so I edit the texmf.cnf and change stack_size to something big. The
problem is, regardless of what I change this to (5000, 10000), I get
! TeX capacity exceeded, sorry [input stack size=3000].
Is there an upper limit of 3000 or something? Should Context be needing
more than that? I don't *think* there's anything screwy with my doc. It
compiles and displays fine under Linux.
Oh, I should add that I'm running it with pdftex (which I also use to
build the fmt file).
- Matthew Baker
--
Dr. Matthew Baker matthew.baker@gmd.de
GMD - FIT.MMK http://fit.gmd.de/hci/pages/matthew.baker.html
next reply other threads:[~1999-04-23 8:31 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
1999-04-23 8:31 Matthew Baker [this message]
1999-04-23 9:18 ` Hans Hagen
1999-04-23 11:22 ` Taco Hoekwater
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=Pine.SGI.4.04.9904231025350.48024-100000@sono \
--to=mbaker@mmkmail.gmd.de \
--cc=Matthew.Baker@gmd.de \
/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).