From: Rik Kabel <ConTeXt@rik.users.panix.com>
To: ntg-context@ntg.nl
Subject: [NTG-context] out of order sectionsblocks
Date: Mon, 4 Sep 2023 22:06:20 -0400 [thread overview]
Message-ID: <d4f342b4-742f-4e92-9f9b-87479ceca342@rik.users.panix.com> (raw)
[-- Attachment #1.1: Type: text/plain, Size: 897 bytes --]
The following example generates a log file which begins with the line
structure > lists > out of order sectionsblocks, maybe use
\setsectionblock
My larger document has over a hundred of these at the beginning.
\setupnote [endnote] [location=none]
\starttext
\startbodymatter
\startchapter[title={Body}]
\startparagraph
\input knuthmath
\startendnote
\input knuth-gpt
\stopendnote
\stopparagraph
\stopchapter
\stopbodymatter
\startbackmatter
\startchapter[title={Notes}]
\placenotes [endnote]
\stopchapter
\stopbackmatter
\stoptext
Can the message be suppressed? Is there a better way to set up the
document to have endnotes for text in other-than-backmatter
sectionblocks appear in the backmatter sectionblock?
--
Rik
[-- Attachment #1.2: Type: text/html, Size: 1450 bytes --]
[-- Attachment #2: Type: text/plain, Size: 495 bytes --]
___________________________________________________________________________________
If your question is of interest to others as well, please add an entry to the Wiki!
maillist : ntg-context@ntg.nl / https://www.ntg.nl/mailman/listinfo/ntg-context
webpage : https://www.pragma-ade.nl / http://context.aanhet.net
archive : https://bitbucket.org/phg/context-mirror/commits/
wiki : https://contextgarden.net
___________________________________________________________________________________
next reply other threads:[~2023-09-05 2:08 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-09-05 2:06 Rik Kabel [this message]
2023-09-05 11:33 ` [NTG-context] " Hans Hagen 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=d4f342b4-742f-4e92-9f9b-87479ceca342@rik.users.panix.com \
--to=context@rik.users.panix.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).