From: Mojca Miklavec <mojca.miklavec.lists@gmail.com>
To: mailing list for ConTeXt users <ntg-context@ntg.nl>
Subject: Re: bug: wrong subject name in headertext
Date: Thu, 13 Oct 2011 22:35:49 +0200 [thread overview]
Message-ID: <CALBOmsYeiyV2JAXAg4MU=PqfyQzLtaMskpftnRW5njF1qKYPNg@mail.gmail.com> (raw)
In-Reply-To: <65D65D5C-A4D6-4E13-82F0-6D6A9D68C5D4@googlemail.com>
On Thu, Oct 13, 2011 at 22:19, Wolfgang Schuster wrote:
> Am 13.10.2011 um 22:10 schrieb Mojca Miklavec:
>
>> Hello,
>>
>> the following example might not be the most minimal possible example,
>> but I hope that it is short enough. I'm using
>> \setupheadertexts
>> []
>> [subject]
>> to print subject into header, but the headers are screwed up in some
>> very weird way. My real document behaves differently that this minimal
>> example, but even here one can notice that headers say:
>> - This is first heading
>> - This is fourth heading
>> - This is second heading
>> - This is fourth heading
>> instead of getting the second heading.
>
> Add “expansion=yes” to \setuphead.
Thank you. Black magic worked.
Assuming that one would want to explain that option in reference
manual - what would be some short and clear explanation? When do I
need to use expansion?
Mojca
___________________________________________________________________________________
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
___________________________________________________________________________________
next prev parent reply other threads:[~2011-10-13 20:35 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-10-13 20:10 Mojca Miklavec
2011-10-13 20:19 ` Wolfgang Schuster
2011-10-13 20:35 ` Mojca Miklavec [this message]
2011-10-13 21: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='CALBOmsYeiyV2JAXAg4MU=PqfyQzLtaMskpftnRW5njF1qKYPNg@mail.gmail.com' \
--to=mojca.miklavec.lists@gmail.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).