From: Bruce Horrocks via ntg-context <ntg-context@ntg.nl>
To: ntg-context mailing list <ntg-context@ntg.nl>
Cc: Bruce Horrocks <ntg@scorecrow.com>
Subject: Any way to configure \setuphead to run a setups on the stop command?
Date: Tue, 26 Jul 2022 11:41:47 +0100 [thread overview]
Message-ID: <DFE3ED5E-DCED-4018-9760-50258B295894@scorecrow.com> (raw)
If I use \definehead [Chapter] [chapter] and then \setuphead[Chapter][...] I can specify setups to run before and after \startChapter.
Is there any way to specify setups that are run before & after \stopChapter?
My real problem is that I have a double-sided book with new chapters starting on a right hand page. If an extra left-hand page gets added then that extra page is blank except for the header which continues from the previous chapter. This makes the page look a bit odd and I'd rather the header was blank.
I can fix this by ensuring each chapter emits a final page (to ensure the headers on the last text-bearing page of the chapter are shown) and then clearing the header temporarily using: \stopChapter\page\setupheader[state=empty]
This works so I wondered if there was a way of adding it to \stopChapter ?
I can edit each individual chapter file easily enough so no need to add it as a feature if it's not already available in some way.
—
Bruce Horrocks
Hampshire, UK
___________________________________________________________________________________
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:[~2022-07-26 10:41 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-07-26 10:41 Bruce Horrocks via ntg-context [this message]
2022-07-26 11:44 ` Henning Hraban Ramm 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=DFE3ED5E-DCED-4018-9760-50258B295894@scorecrow.com \
--to=ntg-context@ntg.nl \
--cc=ntg@scorecrow.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).