ntg-context - mailing list for ConTeXt users
 help / color / mirror / Atom feed
From: "talazem@fastmail.fm" <talazem@fastmail.fm>
To: mailing list for ConTeXt users <ntg-context@ntg.nl>
Subject: Can \getmarking take more than one argument?
Date: Sun, 9 Aug 2015 01:42:49 +0100	[thread overview]
Message-ID: <94B0B9DC-3866-4570-B612-E6CC196AACEB@fastmail.fm> (raw)

Hello,

I currently use the following to define my even and odd page headers.

—————
\startsetups[header]
  {\doifoddpageelse
  		{\getmarking[section]}
  		{\getmarking[chapter]}
	}
  \doiftextelse
  		{\getmarking[chapter]}
\stopsetups
—————

The problem is that some of my ‘section’s are not sections, but ‘subject’s (because I don’t want that section heading to appear in the TOC). As a result, my header is blank on the ‘subject’ pages. 

Is it possible to define getmarking to take either a section or a subject, somehow? Listing them both separated by a coma (\getmarking[section,subject]) produced no result. I also tried:
—————
  {\doifoddpageelse
  		{\getmarking[section]}
 		{\getmarking[subject]}
  		{\getmarking[chapter]}
—————
…but that caused the subject and the chapter to both be printed in the header.

Many thanks for any help.

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

             reply	other threads:[~2015-08-09  0:42 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-08-09  0:42 talazem [this message]
2015-08-09 10:59 ` Hans Hagen
2015-08-09 11:22   ` talazem

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=94B0B9DC-3866-4570-B612-E6CC196AACEB@fastmail.fm \
    --to=talazem@fastmail.fm \
    --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).