From: Hans Hagen <pragma@wxs.nl>
Cc: Context List <ntg-context@ntg.nl>
Subject: Re: input stack size limit?
Date: Fri, 23 Apr 1999 11:18:09 +0200 [thread overview]
Message-ID: <37203AD1.96DBD119@wxs.nl> (raw)
In-Reply-To: <Pine.SGI.4.04.9904231025350.48024-100000@sono>
Matthew Baker wrote:
> 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).
(1) Some memory changes in texmf and runtime, some become hardcoded in
the fmt file. So, when changing a value, always regenerate a format.
(2) I currently use the next values (for all my texs), but when you use
tetex, thomas already has set the values to reasonable ones.
main_memory = 1500000
extra_mem_top = 1000000
extra_mem_bot = 1000000
font_mem_size = 250000
font_max = 750
hash_extra = 30000
pool_size = 500000
string_vacancies = 25000
max_strings = 50000
pool_free = 475000
trie_size = 64000
hyph_size = 1000
buf_size = 10000
nest_size = 750
max_in_open = 15
param_size = 5000
save_size = 20000
stack_size = 5000
obj_tab_size = 150000
(3) I'm not that sure if a large input stack is always needed. You can
take a look at the log file (at the end) and see to what respect the
limits are reached.
(4) In the texmf file, one can set all mem values (like shown here) or
for some specific programs or packages. Currently (when you use tetex)
the context prefix is used for context. You generate a format by either
running the tetex configuration script, or running 'texexec --make'.
Both make sure the right memory values are used.
I hope this helps, otherwise Thomas Esser has to assist,
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.nl
-----------------------------------------------------------------
next prev parent reply other threads:[~1999-04-23 9:18 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
1999-04-23 8:31 Matthew Baker
1999-04-23 9:18 ` Hans Hagen [this message]
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=37203AD1.96DBD119@wxs.nl \
--to=pragma@wxs.nl \
--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).