From: Rik Kabel via ntg-context <ntg-context@ntg.nl>
To: ntg-context@ntg.nl
Cc: Rik Kabel <ConTeXt@rik.users.panix.com>
Subject: Re: TeX capacity exceeded.... but....
Date: Thu, 17 Mar 2022 18:34:36 -0400 [thread overview]
Message-ID: <caa3b815-8c9b-cdae-7ded-4407da5e711b@rik.users.panix.com> (raw)
In-Reply-To: <0f28256c-da13-3383-1446-59e9eb54bb65@gmail.com>
On 2022-03-17 18:14, jbf via ntg-context wrote:
> I'd like to understand what is happening in this particular instance:
>
> While playing with a suggestion to a recent request (re
> \currentlistentrynumber etc.) I suddenly got a compiling error:
>
> TeX capacity exceeded, sorry [file=2000].
>
> I returned everything to how it was before I was trying out those
> suggestions, but still got the error, so I began the \stopdocument
> routine fairly early in the document... same problem still. Then I
> brought the \stopdocument well forward, immediately after the standard
> makeup pages and the document compiled. When I removed \stopdocument,
> the entire document compiled as it should.
>
> So the basic question is: what can be causing the error message? This
> has happened to me on two occasions with this document - it occurred
> once before I had even begun experimenting with the \currentlistentry
> options, so I do not think that the problem lies there. And when it
> occurred that time, I again solved it with \stopdocument routine, but
> further into the document. And similarly, once it compiled that far
> and I removed it, the whole document compiled once more.
>
> If it is too complicated an explanation for an email response, maybe
> just point me to a document that explains the issue.
>
> Julian
>
I cannot explain what is happening, but I can tell you what I do when I
come across an unexpected failure: I delete the .tuc file (and .tua file
as well if present) and try again.
This is an easy thing to do before halving the source (moving \stop) and
such.
--
Rik
___________________________________________________________________________________
If your question is of interest to others as well, please add an entry to the Wiki!
maillist : ntg-context@ntg.nl / http://www.ntg.nl/mailman/listinfo/ntg-context
webpage : http://www.pragma-ade.nl / http://context.aanhet.net
archive : https://bitbucket.org/phg/context-mirror/commits/
wiki : http://contextgarden.net
___________________________________________________________________________________
prev parent reply other threads:[~2022-03-17 22:34 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-03-17 22:14 jbf via ntg-context
2022-03-17 22:29 ` Hans Hagen via ntg-context
2022-03-17 22:34 ` Rik Kabel via ntg-context [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=caa3b815-8c9b-cdae-7ded-4407da5e711b@rik.users.panix.com \
--to=ntg-context@ntg.nl \
--cc=ConTeXt@rik.users.panix.com \
/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).