From: Matt Gushee <mgushee@havenrock.com>
Subject: Re: Disappearing headers -- belated followup
Date: Tue, 10 Aug 2004 15:06:02 -0600 [thread overview]
Message-ID: <20040810210602.GA28260@swordfish> (raw)
In-Reply-To: <41191BF8.1040708@wxs.nl>
On Tue, Aug 10, 2004 at 09:03:20PM +0200, Hans Hagen wrote:
> >>i need a small doc with dummy text to see the effect -)
> >
> >\setupheader[state=empty]
> >
> >
> those seems redundant to me (since you set up the chapter head anyway)
Without that, headers were appearing on the first page of the chapter.
I expected there would be a global setup to suppress headers in such
places, but I couldn't find it. Did I miss something?
> your problem probably is that you expect the title marking to be
> persistant while in reality it is coupled to the chapter mark;
>
> \decouplemarking[title]
>
> will decouple them
Aha! That seems to fix the problem. But could you explain (if the reason
is understandable to someone not very familiar with ConTeXt internals)?
If the chapter and title headings are coupled, that implies (doesn't
it?) that they will appear or not appear in pairs everywhere. Yet in my
document, the title stopped appearing on one page and failed to reappear
for the rest of the book, whereas the chapter headings continued.
I may not absolutely need to know this, but it will help me understand
ConTeXt a little better.
Thanks for the response.
--
Matt Gushee When a nation follows the Way,
Englewood, Colorado, USA Horses bear manure through
mgushee@havenrock.com its fields;
http://www.havenrock.com/ When a nation ignores the Way,
Horses bear soldiers through
its streets.
--Lao Tzu (Peter Merel, trans.)
next prev parent reply other threads:[~2004-08-10 21:06 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-07-23 22:55 Disappearing headers Matt Gushee
2004-07-28 8:54 ` Hans Hagen
2004-08-10 5:23 ` Disappearing headers -- belated followup Matt Gushee
2004-08-10 19:03 ` Hans Hagen
2004-08-10 21:06 ` Matt Gushee [this message]
2004-08-11 7:13 ` Hans Hagen
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=20040810210602.GA28260@swordfish \
--to=mgushee@havenrock.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).