From: Marco <netuse@lavabit.com>
To: ntg-context@ntg.nl
Subject: Chapter layout with \structureuservariable and a makeup
Date: Wed, 6 Jun 2012 22:31:28 +0200 [thread overview]
Message-ID: <20120606223128.693c70c2@Zewz> (raw)
Hi,
I fail to use \structureuservariable to print a value on the page
preceding a chapter. Example:
\setuphead [chapter]
[before=\setups{chap}, command=\myChap]
\startsetups chap
\startmakeup
setups\crlf
structureuservariable foo: \structureuservariable{foo}
\stopmakeup
\stopsetups
\define[2]\myChap{%
\startmakeup
command\crlf
structureuservariable foo: \structureuservariable{foo}
\stopmakeup}
\starttext
\startchapter [title=First][foo=one]
\input knuth
\stopchapter
\startchapter [title=Second][foo=two]
\input knuth
\stopchapter
\stoptext
Problems
--------
\structureuservariable does not work with the “before” key. In the
first chapter the value is empty and in the second chapter it has
the value from the first one. That means, it is designed to be used
with the “command” key.
When used with the “command” key, the values are correct. However,
the following chapter text always appears on the same page, even
when a makeup or a manual page break is used. Additionally you have
to mess around with the two arguments of \myChap, which easily leads
to inconsistent spacing (that's why I used the “before” key in the
first place).
\setuphead doesn't seem to support a “setups=…” key, unfortunately.
What would be the solution for this?
Marco
___________________________________________________________________________________
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://tex.aanhet.net
archive : http://foundry.supelec.fr/projects/contextrev/
wiki : http://contextgarden.net
___________________________________________________________________________________
reply other threads:[~2012-06-06 20:31 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20120606223128.693c70c2@Zewz \
--to=netuse@lavabit.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).