From: jbf <roma83537@gmail.com>
To: Aditya Mahajan <adityam@umich.edu>
Cc: mailing list for ConTeXt users <ntg-context@ntg.nl>
Subject: Re: headers again
Date: Thu, 13 Aug 2020 15:57:18 +1000 [thread overview]
Message-ID: <81fa71d3-1d44-0322-5947-525831b66a2f@gmail.com> (raw)
In-Reply-To: <nycvar.YAK.7.78.908.2008130135130.1544@nqv-guvaxcnq>
Rightly so, and as I was producing such an MWE (stripping away a lot of
other 'clutter') I found what was causing the problem. At one stage,
trying to solve the problem, I had created a MyChapter definition and
had left a command referencing it in the following:
\setuphead
[chapter][header=empty,alternative=middle,style=\tfa,
numbercommand=\groupedcommand{}{\blank[1cm]},after={\blank[3cm]},command=\MyChapter]
Give that I was now no longer using MyChapter to solve the problem, that
command=\MyChapter was causing a conflict. I removed it and, using your
earlier
\setupheadertexts[\setups{header}]
\startsetups header
\getmarking[chapter]
\stopsetups
and referencing it in the \chapter or \title items, was able to achieve
the desired result in every way, including that missing header on one page.
Thank you.
J
On 13/8/20 3:36 pm, Aditya Mahajan wrote:
> On Thu, 13 Aug 2020, jbf wrote:
>
>> Almost as perfect as Shakespeare's Juliet! Is there any reason why the header
>> for the Introduction, done using your approach (it is in frontmatter), does
>> not produce the header on the last recto page? This intro consists of 8 pages.
>> Page 7 does not produce the 'Introduction' header. The other relevant recto
>> pages are all headed 'Introduction' as they should be.
> A minimal working example will help in diagnosing what is going on ...
>
> Aditya
> ___________________________________________________________________________________
> 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://context.aanhet.net
> archive : https://bitbucket.org/phg/context-mirror/commits/
> wiki : http://contextgarden.net
> ___________________________________________________________________________________
___________________________________________________________________________________
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://context.aanhet.net
archive : https://bitbucket.org/phg/context-mirror/commits/
wiki : http://contextgarden.net
___________________________________________________________________________________
next prev parent reply other threads:[~2020-08-13 5:57 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-08-13 0:03 jbf
2020-08-13 2:53 ` Aditya Mahajan
2020-08-13 3:35 ` jbf
2020-08-13 5:36 ` Aditya Mahajan
2020-08-13 5:57 ` jbf [this message]
2020-08-13 18:16 ` Wolfgang Schuster
2020-08-13 23:44 ` Aditya Mahajan
2020-08-14 0:28 ` jbf
2020-08-14 9:04 ` Wolfgang Schuster
2020-08-14 6:34 ` 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=81fa71d3-1d44-0322-5947-525831b66a2f@gmail.com \
--to=roma83537@gmail.com \
--cc=adityam@umich.edu \
--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).