ntg-context - mailing list for ConTeXt users
 help / color / mirror / Atom feed
From: Henning Hraban Ramm <texml@fiee.net>
To: mailing list for ConTeXt users <ntg-context@ntg.nl>
Subject: Re: limit of index entries?
Date: Sun, 2 Aug 2020 18:29:02 +0200	[thread overview]
Message-ID: <A241B619-86FE-46FB-949F-3ABB765BA61B@fiee.net> (raw)
In-Reply-To: <8b88b421-a427-caad-e076-ffeee1e6a440@xs4all.nl>


> Am 02.08.2020 um 10:18 schrieb Hans Hagen <j.hagen@xs4all.nl>:
> 
> On 8/1/2020 6:08 PM, Henning Hraban Ramm wrote:
>>> Am 01.08.2020 um 14:10 schrieb Hans Hagen <j.hagen@xs4all.nl>:
>>> 
>>> On 8/1/2020 1:54 PM, Henning Hraban Ramm wrote:
>>>> Hi,
>>>> my aforementioned person index has more than 600 entries. If I get over ~500, ConTeXt (MkIV, several versions) breaks with
>>>> ! error (push_node): stack overflow
>>>> mtx-context     | fatal error: return code: 256
>>>> Is there a hard limit? Can I change it?
>>> it might relate to protrusion (which needs to enter nested boxes to determine an edge) but how that then can relate to the number of entries puzzles me, unless we pop too less ... in which case i need to trace (with a mwe)
>> I can’t reproduce it with a simple example like
>> \setupalign[hanging]
>> \starttext
>> \placeregister[index][criterium=all]
>> \dorecurse{10000}{\par\strut\index{Test\recurselevel}}
>> \stoptext
>> \recurselevel is empty in that context, \expanded didn’t help, but I guess we need different entries.
>> Find attached the actual data, reduced to the minimum setup – the problem is indeed \setupalign[hanging].
>> I guess I can omit "hanging" for the index, but of course if would be nice if it would work.
> it has to do with how you do that index:
> 
> - you do a lot of \index but you do that in vmode
> - do, they get collected for the next paragraph
> - that is done in a robust way which involves packing
> - eventually you flush with a \strut
> - so we get deeply nested boxes
> - and that means trouble for protrusion pre-analysis
> 
> now, I can try to avoid it but we then can have side effects but we'll see
> 
> can you try to avoid collecting:
> 
> \leavevmode
> \index{...}%
> 
> make sure no spaces get introduced

Ah, yes, that works.
So it won’t be a problem in the completed book – the big list of entries is just all the names the author wants indexed and I’ll delete it as soon as the index entries are in the text where they belong.

Thank you very much!

Hraban
___________________________________________________________________________________
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
___________________________________________________________________________________

      reply	other threads:[~2020-08-02 16:29 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-08-01 11:54 Henning Hraban Ramm
2020-08-01 12:08 ` Hans Hagen
     [not found] ` <c3321d32-b04d-d971-8559-b5c48ab94cc9@xs4all.nl>
     [not found]   ` <C22E2481-5B5E-4131-B0FB-7C585E3D4730@fiee.net>
2020-08-02  8:18     ` Hans Hagen
2020-08-02 16:29       ` Henning Hraban Ramm [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=A241B619-86FE-46FB-949F-3ABB765BA61B@fiee.net \
    --to=texml@fiee.net \
    --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).