ntg-context - mailing list for ConTeXt users
 help / color / mirror / Atom feed
From: Hans Hagen <j.hagen@xs4all.nl>
To: Alan Braslau <braslau.list@comcast.net>,
	Wolfgang Schuster <wolfgang.schuster.lists@gmail.com>
Cc: mailing list for ConTeXt users <ntg-context@ntg.nl>
Subject: Re: \setupheadertexts \setupfootertexts
Date: Sat, 3 Aug 2019 00:31:29 +0200	[thread overview]
Message-ID: <461aed10-ff8b-2933-df8d-f884396aab1e@xs4all.nl> (raw)
In-Reply-To: <20190802155949.468e6e40@poo.hsd1.co.comcast.net>

On 8/2/2019 11:59 PM, Alan Braslau wrote:
> On Fri, 2 Aug 2019 23:36:47 +0200
> Wolfgang Schuster <wolfgang.schuster.lists@gmail.com> wrote:
> 
>>> we have a lot or areas ... and if you really want you can do this ...
>>>
>>> \setuplayouttext
>>>
>>> Has been there for ages ... (but I never use that method).
>>
>> I has the same question a few years ago but I never used it
>> because it has a few limitations like missing style/color support.
> 
> I am looking for a simple and obvious way of setting header and footer
> texts. The \setupheadertexts has limitations and I view this as
> historical, for ConTeXt commands have evolved over time usually towards
> better solutions, even if we leave in place for reasons of backward
> compatibility habits that can be hard to quit.
> 
> One example is \setuppapersize [page=letter,paper=letter]
> (sorry, and I *do* much prefer A4).
> This is, I believe, far superior to \setuppapersize [letter] [letter]
> 
> 
> Do you find that keys in \setupheader make sense? If so, what choice?
> (as we like to limit the proliferation of key names).
actually there is not really a \setupheader as these are shortcuts to a 
few kind of generic commands that set up properties of these areas (a 
matrix) on the one hand, and set the content with a different command

(also, this part of context is quite optimized deep down because 
checking 25 areas for all possible properties each page flush is costly, 
so it would be a major rewrite with little gain; it would also mean 
dropping \setuphead etc and using one command for everything ... not 
something i want to do in the middle of other transitions like 
mkiv->mkxl and such)

hans

-----------------------------------------------------------------
                                           Hans Hagen | PRAGMA ADE
               Ridderstraat 27 | 8061 GH Hasselt | The Netherlands
        tel: 038 477 53 69 | www.pragma-ade.nl | www.pragma-pod.nl
-----------------------------------------------------------------
___________________________________________________________________________________
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
___________________________________________________________________________________

  parent reply	other threads:[~2019-08-02 22:31 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-08-02 18:29 Alan Braslau
2019-08-02 19:08 ` Wolfgang Schuster
2019-08-02 20:26   ` Alan Braslau
2019-08-02 21:10     ` Hans Hagen
2019-08-02 21:36       ` Wolfgang Schuster
2019-08-02 21:59         ` Alan Braslau
2019-08-02 22:23           ` Hans Hagen
2019-08-02 22:31           ` Hans Hagen [this message]
2019-08-02 22:46         ` Hans Hagen

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=461aed10-ff8b-2933-df8d-f884396aab1e@xs4all.nl \
    --to=j.hagen@xs4all.nl \
    --cc=braslau.list@comcast.net \
    --cc=ntg-context@ntg.nl \
    --cc=wolfgang.schuster.lists@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).