From: Aditya Mahajan <adityam@umich.edu>
To: mailing list for ConTeXt users <ntg-context@ntg.nl>
Subject: Re: getmarking and empty chapter number
Date: Mon, 23 May 2011 20:26:14 -0400 (EDT) [thread overview]
Message-ID: <alpine.LNX.2.02.1105232025330.26276@ybpnyubfg.ybpnyqbznva> (raw)
In-Reply-To: <3CF1CC62-4B8A-4E3F-A086-37D9942E11D1@mpq.mpg.de>
On Mon, 23 May 2011, Oliver Buerschaper wrote:
> Hi all,
>
> I'm just trying to wrap my mind around why the following doesn't work as I expect:
>
> --
> \setupheadertexts
> []
> [{\doifsomething{\getmarking[sectionnumber]}{\getmarking[sectionnumber]\enskip}\getmarking[section]}]
> [{\doifsomething{\getmarking[chapternumber]}{\getmarking[chapternumber]\enskip}\getmarking[chapter]}]
> []
> --
>
> When this encounters an unnumbered \startchapter (say in the front
> matter) then this \doifsomething should detect this void and in
> particular not insert the \enskip. For some reason the space ends up in
> the PDF nevertheless :-(
>
> Any ideas?
From supp-box.mkiv:
%D \macros
%D {doiftextelse, doiftext}
%D
%D When \type {\doifelse} cum suis hopelessly fail, for
%D instance because we pass data, we can fall back on the next
%D macro:
%D
%D \starttyping
%D \doiftextelse {data} {then branch} {else branch}
%D \doiftext {data} {then branch}
%D \stoptyping
Aditya
___________________________________________________________________________________
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-05-24 0:26 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-05-23 19:39 Oliver Buerschaper
2011-05-24 0:26 ` Aditya Mahajan [this message]
2011-05-24 6:28 ` Oliver Buerschaper
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=alpine.LNX.2.02.1105232025330.26276@ybpnyubfg.ybpnyqbznva \
--to=adityam@umich.edu \
--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).