ntg-context - mailing list for ConTeXt users
 help / color / mirror / Atom feed
From: "Lukáš Procházka" <LPr@pontex.cz>
To: "mailing list for ConTeXt users" <ntg-context@ntg.nl>
Subject: Re: \setuphead for all existing sections
Date: Mon, 20 Apr 2015 20:43:07 +0200	[thread overview]
Message-ID: <op.xxcceso8f14xzu@lkzd-2013> (raw)
In-Reply-To: <55313646.4030407@gmx.es>

Hello Pablo,

\setupheads doesn't work for this - see the test:

----
\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


On Fri, 17 Apr 2015 18:35:18 +0200, Pablo Rodriguez <oinos@gmx.es> wrote:

> On 04/17/2015 12:00 PM, Procházka Lukáš Ing. - Pontex s. r. o. wrote:
>> Hello,
>>
>> is there a way to affect (setup) all sections that have been defined, like:
>>
>> ----
>> \setuphead[*][distance=1.5em]
>> ----
>>
>> instead of:
>>
>> ----
>> \setuphead[part,chapter,section,subsection,subsubsection][distance=1.5em]
>> ----
>
> Hi Lukáš,
>
> \setupheads[distance=1.5em] should do the work.
>
> I hope it helps,
>
>
> Pablo


-- 
Ing. Lukáš Procházka | mailto:LPr@pontex.cz
Pontex s. r. o.      | mailto:pontex@pontex.cz | http://www.pontex.cz
Bezová 1658
147 14 Praha 4

Tel: +420 241 096 751
Fax: +420 244 461 038

___________________________________________________________________________________
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-04-20 18:43 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 [this message]
2015-04-20 19:00     ` Pablo Rodriguez
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=op.xxcceso8f14xzu@lkzd-2013 \
    --to=lpr@pontex.cz \
    --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).