octave-maintainers
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[changeset] Adapted munge-texi to expand @seealso commands to texinfo re


From: John W. Eaton
Subject: [changeset] Adapted munge-texi to expand @seealso commands to texinfo references, tex error
Date: Thu, 30 Oct 2008 12:12:46 -0400

On 26-Oct-2008, Thorsten Meyer wrote:

|  - And, worst of all, the building of the pdf documents failed with the
| error "message./octave.aux:4743: TeX capacity exceeded, sorry [save
| size=5000].". To fix this I had to change the value in
| /etc/texmf/texmf.cnf (on debian the actual change had to be done in
| /etc/texmf/texmf.d/95NonPath.cnf): I set save_size = 50000. Then it
| worked fine.

It worked for me with 5014 but not 5013.  So it seems even 7500 would
be more than large enough for this parameter.

| But, how could such a change to the tex configuration be integrated into
| the make configuration? Does the same problem come up under windows or
| mac or other platforms? Is there a way to locally change this tex
| setting for example by an environment variable (I have found nothing in
| the tex documentation but I am certainly not a tex expert)?

I don't know of a good and portable way to do this.  There are (have
been) a number of TeX implementations that have handled configuration
differently.  In the old days you would have had to recompile TeX in
order to increase its capacity.

With a modern TeX that uses texmf.cnf and has kpsewhich, I suppose you
could do something like

  sed 's/save_size *= *[0-9]*/save_size = 10000/' $(kpsewhich texmf.cnf) > 
texmf.cnf-t && mv texmf.cnf-t texmf.cnf
  TEXMFCNF=. pdflatex ...

(you might also want to add save_size if it is not already present).
But doing something like this seems a bit of a kluge, and again, not
portable.

I don't see a way to tell TeX to read a series of configuration files
so that you can let it read the system-wide texmf.cnf file then read
another one that contains just "save_size = 10000".

Should we disable the expansion of @seealso by default, and only do it
when specifically requested?  Or should we just let builds fail, and
tell people to increase save_size in their TeX isntallation?  If we do
that, we should also ask the people who package TeX to consider an
increase in this parameter for us.

jwe


reply via email to

[Prev in Thread] Current Thread [Next in Thread]