On Tue, 15 May 2018 22:52:47 -0400 Scott Kostyshak <[email protected]> wrote:
> On Wed, May 16, 2018 at 02:26:35AM +0000, Robert Kern wrote: > > Dear lyx-users, > > > > I'm writing a book, and this evening I decided to export it to > > a .pdf file to check it out. I went to File->Export->PDF (pdflatex) > > and hit Enter. A few seconds later I received an error message > > which said, > > > > "! TeX capacity exceeded, sorry [parameter stack size=10000]. > > > > If you really absolutely need more capacity, > > > > you can ask a wizard to enlarge me." > > > > I'm running LyX on Linux and have plenty of memory and disk space, > > so I wondered where I could find a "wizard" to increase the Tex > > stack size. I went to www.lyx.org, but found nothing there, so I > > went to www.ctan.org and searched for "wizard" and "stack size." > > > > So, can anyone tell me how to increase the Tex stack size, or where > > I can find a "wizard" that can help me? Otherwise, I'm stuck with a > > three-quarter completed book which I can't complete using LyX. > > > > Thanks in advance, > > Hi Robert, > > Ouch, that sounds frustrating. Usually this message occurs not because > of lack of RAM or disk space, but because of an error in LaTeX code. > Can you create a minimal example that still generates the error? For > more info, see: > > https://wiki.lyx.org/FAQ/MinimalExample > > Do you have a previous version of your book that does compile? If the > differences are not too big, you might get a hint at what addition > caused the change. If you're not using version control, and you're > interested in more information, let us know. It is very helpful for > situations like this. And yes, unfortunately, a similar situation will > happen again in the future. > > I hope that we can help figure this out! What Scott said. I've had 100,000 word books with graphics, indices and table of contents compile just fine in LyX. Except for those times I made an error (usually something with LaTeX or ERT). When that stuff happens to me (and it happens to me all the time because I'm not careful), I archive the current document, then keep cutting it half until I get it compile, then add stuff til it bombs, and take stuff away, and I can usually get it down to a paragraph and some document settings. At that point, my mistake is usually obvious, but if not, I can send that tiny document (called a Minimum Example) to the list and somebody will instantly diagnose the problem. One thing I do is compile early and often, so that the number of causes is limited. When working on a long term project like a book, I usually compile via a shellscript (or if you're Windows, I think it's called Powerscript). Much faster, easier, and informative. HTH, SteveT Steve Litt June 2018 featured book: Twenty Eight Tales of Troubleshooting http://www.troubleshooters.com/28
