From: Pablo Rodriguez <oinos@gmx.es>
To: mailing list for ConTeXt users <ntg-context@ntg.nl>
Subject: Re: \setuphead for all existing sections
Date: Mon, 20 Apr 2015 21:00:33 +0200 [thread overview]
Message-ID: <55354CD1.8060301@gmx.es> (raw)
In-Reply-To: <op.xxcceso8f14xzu@lkzd-2013>
On 04/20/2015 08:43 PM, Lukáš Procházka wrote:
> Hello Pablo,
>
> \setupheads doesn't work for this - see the test:
Hi Lukáš,
sorry, I thought that the plural of \setup... had the same options than
its singular form. My fault, since I was totally wrong.
I agree that it would be useful to have the same options from \setuphead
in \setupheads.
Pablo
> ----
> \setupheads[distance=1in]
> \setuphead[subsection][distance=2in]
>
> \starttext
> \section{Sec}
> \subsection{Subsec}
> \stoptext
> ----
>
> Subsection has the specified distance of 1 in, whilst the section doesn't.
>
> Section was altered by \setupheads, whilst subsection by \setuphead.
>
> Wiki http://wiki.contextgarden.net/Command/setupheads says that
> \setuphead has some more options than \setupheads.
>
> - I guess it would be nice that \setupheads handles the "distance" key, too.
>
> Best regards,
>
> Lukas
--
http://www.ousia.tk
___________________________________________________________________________________
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:[~2015-04-20 19:00 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-04-17 10:00 Procházka Lukáš Ing. - Pontex s. r. o.
2015-04-17 16:35 ` Pablo Rodriguez
2015-04-20 18:43 ` Lukáš Procházka
2015-04-20 19:00 ` Pablo Rodriguez [this message]
2015-04-20 22:38 ` Wolfgang Schuster
2015-04-21 6:55 ` Procházka Lukáš Ing. - Pontex s. r. o.
2015-04-21 8:15 ` Wolfgang Schuster
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=55354CD1.8060301@gmx.es \
--to=oinos@gmx.es \
--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).