ntg-context - mailing list for ConTeXt users
 help / color / mirror / Atom feed
From: fv leung via ntg-context <ntg-context@ntg.nl>
To: mailing list for ConTeXt users <ntg-context@ntg.nl>
Cc: fv leung <fvleung@gmail.com>
Subject: Re: how to place getmarking[title] in header instead of getmarking[chapter]
Date: Wed, 5 Jan 2022 06:53:04 +0800	[thread overview]
Message-ID: <CAN-yaTniFXok983D2mPF4L4-J1JyXFHGm=4j1cz7i7D_yqOExQ@mail.gmail.com> (raw)
In-Reply-To: <9507c20a6590a22b03c2c010996bf57f2abdf8b0.camel@mailbox.org>


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

can use this for the header:


\setupheadertexts
[text]
[{\namedstructurevariable{chapter}{title}}]
[]
[]
[{\namedstructurevariable{chapter}{title}}]

juh via ntg-context <ntg-context@ntg.nl> 於 2022年1月5日 週三 上午12:28寫道:

> Hi all,
>
> I know how to put the current chapter in the header.
>
> But how can I also put the value of \starttitle in the header.
>
> In this mwe the \starttitle command does not modify the header.
>
> Is it possible to do something like:
>
> \getmarking[chapter or title]
>
> I cannot include
> \setmarking[chapter]{title headline}
> right before \starttitle as the source is created automatically.
>
>
> \setupheadertexts
> [text]
> [{\getmarking[chapter]}]
> []
> []
> [{\getmarking[chapter]}]
>
> \setupcombinedlist[content][list={chapter}]
> \starttext
> \placecontent
> \startchapter
>  [title=Lorem]
>
>  \startsection
>  [title=Lorem subsection]
>  \stopsection
> \stopchapter
> \startchapter
>  [title=Ipsum]
> \stopchapter
> \starttitle
>  [title=title headline]
>
>  Pellentesque dapibus suscipit ligula. Donec posuere augue in quam.
>  Etiam vel tortor sodales tellus ultricies commodo.
>
>  \page
>
> Nullam eu ante vel est convallis dignissim.
>
> \stoptitle
> \stoptext
>
>
>
> ___________________________________________________________________________________
> 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
>
> ___________________________________________________________________________________
>

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

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

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

      reply	other threads:[~2022-01-04 22:53 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-01-04 16:27 juh via ntg-context
2022-01-04 22:53 ` fv leung 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='CAN-yaTniFXok983D2mPF4L4-J1JyXFHGm=4j1cz7i7D_yqOExQ@mail.gmail.com' \
    --to=ntg-context@ntg.nl \
    --cc=fvleung@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).