ntg-context - mailing list for ConTeXt users
 help / color / mirror / Atom feed
From: Pawel Urbanski via ntg-context <ntg-context@ntg.nl>
To: mailing list for ConTeXt users <ntg-context@ntg.nl>
Cc: Pawel Urbanski <urbanski.pawel@gmail.com>
Subject: Re: Use section custom value in a header text.
Date: Thu, 22 Dec 2022 01:04:05 +0100	[thread overview]
Message-ID: <CADUDiDE6Q8oXRVGcnd=KncDUjqGkHQgJCsD3c+3bROY9J8Fp8g@mail.gmail.com> (raw)
In-Reply-To: <2e4571b7-bcb8-4a69-38ac-59a8fdbf88a2@rik.users.panix.com>


[-- Attachment #1.1: Type: text/plain, Size: 693 bytes --]

>
>
> Hi Everyone,

Thanks for the answers. I learnt something new.
I ended up using the:
\namedstructureuservariable{chapter}{my_custom_variable} command with
\setupheadertexts.
It worked well - at least for my case.

While reading the wiki I started wondering what is the role of:
lefttext / middletext / righttext keys in \setupheader and \setupfooter
commands.
I would understand htem as keys that can be assigned some value for their
respective slots. I tried to put some texts manually, but there was no
effect - or maybe there is some trick to that. It was just a bit of
exploration - the solution I described works well for my case.

Thanks again for your time and experience...
Pawel

[-- Attachment #1.2: Type: text/html, Size: 999 bytes --]

[-- Attachment #2: Type: text/plain, Size: 496 bytes --]

___________________________________________________________________________________
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
___________________________________________________________________________________

      reply	other threads:[~2022-12-22  0:04 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-12-20 18:44 Pawel Urbanski via ntg-context
2022-12-20 19:12 ` Henning Hraban Ramm via ntg-context
2022-12-20 19:31   ` Pawel Urbanski via ntg-context
2022-12-20 19:34     ` Henning Hraban Ramm via ntg-context
2022-12-20 20:48     ` Rik Kabel via ntg-context
2022-12-22  0:04       ` Pawel Urbanski via ntg-context [this message]

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='CADUDiDE6Q8oXRVGcnd=KncDUjqGkHQgJCsD3c+3bROY9J8Fp8g@mail.gmail.com' \
    --to=ntg-context@ntg.nl \
    --cc=urbanski.pawel@gmail.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).