From: "Procházka Lukáš Ing. - Pontex s. r. o." <LPr@pontex.cz>
To: "mailing list for ConTeXt users" <ntg-context@ntg.nl>
Subject: Re: \setuphead for all existing sections
Date: Tue, 21 Apr 2015 08:55:52 +0200 [thread overview]
Message-ID: <op.xxfj7ew7tpjj8f@lpr> (raw)
In-Reply-To: <B289CAE6-3C14-4E96-9133-8F2BDF3848EC@gmail.com>
Hello,
On Tue, 21 Apr 2015 00:38:18 +0200, Wolfgang Schuster <schuster.wolfgang@gmail.com> wrote:
> The \setupheads command is only a synonym for \setuphead but there can be a difference between
>
> \setuphead[..,..=..,..]
>
> and
>
> \setuphead[<section][..,..=..,..]
>
> Wolfgang
confirmed:
----
\setuphead[distance=2in]
\starttext
\section{Sec}
\subsection{Subsec}
\stoptext
----
the code above doesn't change the section "distance", either.
Lukas
--
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
___________________________________________________________________________________
next prev parent reply other threads:[~2015-04-21 6:55 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
2015-04-20 22:38 ` Wolfgang Schuster
2015-04-21 6:55 ` Procházka Lukáš Ing. - Pontex s. r. o. [this message]
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.xxfj7ew7tpjj8f@lpr \
--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).