ntg-context - mailing list for ConTeXt users
 help / color / mirror / Atom feed
From: Hans Hagen via ntg-context <ntg-context@ntg.nl>
To: mailing list for ConTeXt users <ntg-context@ntg.nl>
Cc: Hans Hagen <j.hagen@xs4all.nl>
Subject: Re: Space before/after combinations + centring
Date: Thu, 18 Nov 2021 08:57:48 +0100	[thread overview]
Message-ID: <65c44c0b-8987-b40c-8a33-5f8e33ed300e@xs4all.nl> (raw)
In-Reply-To: <20211117234720.5b0eb5eb@homerow>

On 11/17/2021 11:50 PM, Marco Patzer via ntg-context wrote:
> On Wed, 17 Nov 2021 20:17:52 +0100
> Wolfgang Schuster <wolfgang.schuster.lists@gmail.com> wrote:
> 
>> 2. There are no changes to adjust the vertical before and after a
>> combination environment.
> 
> That's unfortunate.
> 
>> Local patches can also be tricky because ConTeXt tries to freeze
>> the definitions of many user level commands which means they can't
>> be redefined when you use a strict overload mode (look at the
>> lowlevel security manual for this feature).
> 
> An overload like mine is probably exactly what the strict overload
> mode is supposed to protect against.
> 
>> The most reliable way to center you combination blocks is to put
>> them either in a float or put a framedtext environment around it.
> 
> The project comprises several hundred source files. That's why I
> stayed away from rewriting the sources in the first place. I'll try
> to bulk-change the sources.
combinations are really just a way to package things, not meant for 
direct usage in the page flow

\startlinecorrection[blank]
...
\stoplinecorrection

is one way to use them, or in floats; the same is true for natural tables

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
___________________________________________________________________________________

      reply	other threads:[~2021-11-18  7:57 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-11-17 15:54 Marco Patzer via ntg-context
2021-11-17 19:17 ` Wolfgang Schuster via ntg-context
2021-11-17 22:50   ` Marco Patzer via ntg-context
2021-11-18  7:57     ` Hans Hagen via ntg-context [this message]

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=65c44c0b-8987-b40c-8a33-5f8e33ed300e@xs4all.nl \
    --to=ntg-context@ntg.nl \
    --cc=j.hagen@xs4all.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).