ntg-context - mailing list for ConTeXt users
 help / color / mirror / Atom feed
From: Taco Hoekwater via ntg-context <ntg-context@ntg.nl>
To: mailing list for ConTeXt users <ntg-context@ntg.nl>
Cc: Taco Hoekwater <taco@bittext.nl>
Subject: Re: Test for displaying a header
Date: Thu, 26 Aug 2021 16:34:02 +0200	[thread overview]
Message-ID: <40A5A4E3-D83B-49CC-86C0-E402899F7B47@bittext.nl> (raw)
In-Reply-To: <CACyK-ep0t7YwrzduOuQ-kF59wLDYfmW6B9xVU+9ihUpbvGoWtA@mail.gmail.com>


Hi,

> On 26 Aug 2021, at 16:07, Fabrice Couvreur via ntg-context <ntg-context@ntg.nl> wrote:
> 
> Hi, 
> I know I asked the question a few years ago, but I don't remember ! 
> The idea is to test whether the document contains only one page or not. 

Perhaps not the nicest solution, but this works:

\doifvalueelse
  {\lastpage}
  {1}
  {\message{true}}
  {\message{false}}

> If it contains only one page, the header is enabled. 
> If it contains several pages, the header is enabled only on the first page but not on the others. 
> Thanks
> Fabrice
> ___________________________________________________________________________________
> 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
> ___________________________________________________________________________________

— 
Taco Hoekwater              E: taco@bittext.nl
genderfluid (all pronouns)



___________________________________________________________________________________
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:[~2021-08-26 14:34 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-08-26 14:07 Fabrice Couvreur via ntg-context
2021-08-26 14:34 ` Taco Hoekwater via ntg-context [this message]
2021-08-26 15:56   ` Wolfgang Schuster via ntg-context
2021-08-26 17:06     ` Fabrice Couvreur via ntg-context
2021-08-26 17:56       ` Wolfgang Schuster via ntg-context
     [not found]         ` <CACyK-eryA8rxnsbOXbU7aOW0=PHFKsLSchU-J5vn7CsjOpJT2A@mail.gmail.com>
2021-08-27 16:05           ` Wolfgang Schuster via ntg-context
     [not found]             ` <CACyK-eqnhx1dAAVBe3HK_OVR+e+HZ6han1enQkx_GukTd9cG-Q@mail.gmail.com>
     [not found]               ` <38a9bada-8507-ef96-c09a-7c48c865049b@gmail.com>
     [not found]                 ` <CACyK-eoL6uhusTErcq+P0HQ8_O9EN+ZV-MXtEOKo-iby4BHBVA@mail.gmail.com>
     [not found]                   ` <CACyK-epiR+X+r_TRJOH+0rz8v_FKAFH7ooR3xqkp1hPdNNm4dg@mail.gmail.com>
2021-08-28 12:24                     ` Wolfgang Schuster 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=40A5A4E3-D83B-49CC-86C0-E402899F7B47@bittext.nl \
    --to=ntg-context@ntg.nl \
    --cc=taco@bittext.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).