From: Wolfgang Schuster <wolfgang.schuster.lists@gmail.com>
To: mailing list for ConTeXt users <ntg-context@ntg.nl>,
Joel via ntg-context <ntg-context@ntg.nl>
Subject: [NTG-context] Re: How to track down source of [entry not flushed] displaying in indexes?
Date: Wed, 13 Mar 2024 23:46:53 +0100 [thread overview]
Message-ID: <9fef66ac-8623-956a-88af-dba502f91158@gmail.com> (raw)
In-Reply-To: <872749583.2300537.1710368866064@mail.yahoo.com>
Joel via ntg-context schrieb am 13.03.2024 um 23:27:
> After many hours of trial-and-error, I was able to recreate the problem
> in a minimum working example:
>
> file main.tex only contains:
>
> \starttext
>
> \index{birds}
> \index{insects}
>
> \input secondary
>
> \placeindex
>
> \stoptext
>
> file secondary.tex only contains:
>
>
> \index{turtles}
>
> For reasons I can't understand, the index produces the same [entry not
> flushed] error. It seems here happening when contents are input.
The message appears even without the external file.
> My code is so simple, I can't understand what I've typed wrong.
Indices need an anchor to be flushed. When you put \index entries
between environments the next anchor appears at the start of a new
paragraph (I used \dontleavehmode for this in the following example).
\starttext
\index{birds}
\index{insects}
\index{turtles}
\dontleavehmode % comment this line for [entry not flushed]
\placeindex
\stoptext
Wolfgang
___________________________________________________________________________________
If your question is of interest to others as well, please add an entry to the Wiki!
maillist : ntg-context@ntg.nl / https://mailman.ntg.nl/mailman3/lists/ntg-context.ntg.nl
webpage : https://www.pragma-ade.nl / https://context.aanhet.net (mirror)
archive : https://github.com/contextgarden/context
wiki : https://wiki.contextgarden.net
___________________________________________________________________________________
next prev parent reply other threads:[~2024-03-13 22:49 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1131119472.2149516.1710337659310.ref@mail.yahoo.com>
2024-03-13 13:47 ` [NTG-context] " Joel via ntg-context
2024-03-13 18:49 ` [NTG-context] " Joel via ntg-context
2024-03-13 22:27 ` Joel via ntg-context
2024-03-13 22:46 ` Wolfgang Schuster [this message]
2024-03-13 23:54 ` Joel via ntg-context
2024-03-14 0:11 ` Joel via ntg-context
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=9fef66ac-8623-956a-88af-dba502f91158@gmail.com \
--to=wolfgang.schuster.lists@gmail.com \
--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).