ntg-context - mailing list for ConTeXt users
 help / color / mirror / Atom feed
From: Henning Hraban Ramm via ntg-context <ntg-context@ntg.nl>
To: Pawel Urbanski via ntg-context <ntg-context@ntg.nl>
Cc: Henning Hraban Ramm <texml@fiee.net>
Subject: Re: Use section custom value in a header text.
Date: Tue, 20 Dec 2022 20:12:45 +0100	[thread overview]
Message-ID: <d70b5573-783d-c9b2-8efe-c1c0cdaefe4d@fiee.net> (raw)
In-Reply-To: <CADUDiDGYeYawCcNu_Fmca3sRdqpFzp7f7Je=iJQtuPWZ7WWdgA@mail.gmail.com>

Am 20.12.22 um 19:44 schrieb Pawel Urbanski via ntg-context:
> Dear Friends,
> I spent some time searching and coding simple documents, but failed and 
> therefore I'm asking for help...
> A section such as chapter cn have custom keys with values. One uses the: 
> \structureuservariable command to access such values.
> How can I use such a value to create a custom header in a format:
> Prefix: \structureuservariable{foo}
> 
> I am asking for the only thing that worked when I tried was calling the: 
> \setupheadertexts command inside a chapter environment block with some 
> prefix. Unfortunately the value from the custom field was not expanded.
> It was correctly inserted in a regular paragraph.
> For example:
> \startchapter
> [title={A sample title}][custom_something={random_value}]
> ...
> \stopchapter
> 
> How can I put the value of: custom_something in the header with some prefix?

\define[2]\MyChapter{No.#1 – Prefix 
\structureuservariable{custom_something}: #2}

\setuphead[chapter][
  command=\MyChapter,
]

Is this what you meant?

Hraban
___________________________________________________________________________________
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-20 19:12 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 [this message]
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

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=d70b5573-783d-c9b2-8efe-c1c0cdaefe4d@fiee.net \
    --to=ntg-context@ntg.nl \
    --cc=texml@fiee.net \
    /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).