From: Hans Hagen <j.hagen@xs4all.nl>
To: mailing list for ConTeXt users <ntg-context@ntg.nl>,
denis.maier@ub.unibe.ch
Subject: Re: Setuptolerance vs setupalign
Date: Tue, 2 Mar 2021 11:48:52 +0100 [thread overview]
Message-ID: <a8609a33-e410-d109-8dcd-f6cc2a6b9c7f@xs4all.nl> (raw)
In-Reply-To: <4bdf70c00be74a088b10cd8950a8a157@ub.unibe.ch>
On 3/2/2021 11:40 AM, denis.maier@ub.unibe.ch wrote:
> Hi,
>
> I’ve just noticed that it’s possible to do
>
> \setupalign [tolerant,stretch]
>
> and
>
> \setuptolerance [tolerant,stretch]
>
> Are these equivalent?
>
> Will this here have the desired effect?
>
> \setuptolerance[tolerant,stretch]
>
> \setupalign[hz,hanging]
>
> Or will \setupalign overwrite the tolerance settings?
both overwrite ... same underlying code ... at some point it made sense
to support the tolerance keys in align (which is often an option in
environments and commands)
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
___________________________________________________________________________________
next prev parent reply other threads:[~2021-03-02 10:48 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-03-02 10:40 denis.maier
2021-03-02 10:48 ` Hans Hagen [this message]
2021-03-02 10:50 ` denis.maier
2021-03-02 17:11 ` 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=a8609a33-e410-d109-8dcd-f6cc2a6b9c7f@xs4all.nl \
--to=j.hagen@xs4all.nl \
--cc=denis.maier@ub.unibe.ch \
--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).