ntg-context - mailing list for ConTeXt users
 help / color / mirror / Atom feed
From: Henning Hraban Ramm <texml@fiee.net>
To: ntg-context@ntg.nl
Subject: [NTG-context] Re: context version 20240118 ("Registerhaltigkeit")
Date: Mon, 22 Jan 2024 12:06:01 +0100	[thread overview]
Message-ID: <43c6f5d3-188f-47cb-93d6-e043a93b74fd@fiee.net> (raw)
In-Reply-To: <a91eed2f-6bd8-47c4-903b-43004fc37133@t-online.de>

Am 22.01.24 um 11:46 schrieb Thomas Meyer:
> I might get a bit impatient if I have the impression that others get an 
> answer faster. Sorry for that.

It’s not unusual to get that impression. It depends on the current 
attention, capacity and mood of the few who can answer your questions.

> So the problem 
> is still \hfill that the last paragraph is not on grid in the new and 
> the old version (and comma).

Grid is not as easy as it looks first. Low level tricks like fills or 
skips can mess it up.


Maybe \startlinecorrection helps… (No, it doesn’t.)

It also doesn’t help to add a \blank or \par after \vfill.


Hans, how about adding \blank[fill] for a vertical fill that keeps the 
grid (in grid mode, of course)?



https://wiki.contextgarden.net/Grid_typesetting is not very helpful, 
some links are dead, “someone” should change that.

The details manual has some hints about grid typesetting, but it’s not 
an easy read.

Hraban
___________________________________________________________________________________
If your question is of interest to others as well, please add an entry to the Wiki!

maillist : ntg-context@ntg.nl / https://mailman.ntg.nl/mailman3/lists/ntg-context.ntg.nl
webpage  : https://www.pragma-ade.nl / https://context.aanhet.net (mirror)
archive  : https://github.com/contextgarden/context
wiki     : https://wiki.contextgarden.net
___________________________________________________________________________________

  reply	other threads:[~2024-01-22 11:10 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-01-14  9:30 [NTG-context] "Registerhaltigkeit" Thomas Meyer
2024-01-14  9:59 ` [NTG-context] "Registerhaltigkeit" Wolfgang Schuster
2024-01-14 10:02 ` Henning Hraban Ramm
2024-01-14 10:21   ` Thomas Meyer
2024-01-14 12:53     ` Wolfgang Schuster
2024-01-14 16:36       ` Thomas Meyer
2024-01-17 19:57         ` Thomas Meyer
2024-01-18 11:59           ` [NTG-context] context version 20240118 (was: "Registerhaltigkeit") Thomas Meyer
2024-01-18 12:06             ` [NTG-context] Re: context version 20240118 Hans Hagen via ntg-context
2024-01-18 12:30               ` Thomas Meyer
2024-01-22  9:47               ` [NTG-context] Re: context version 20240118 ("Registerhaltigkeit") Thomas Meyer
2024-01-22  9:56                 ` Hans Hagen via ntg-context
2024-01-22 10:46                   ` Thomas Meyer
2024-01-22 11:06                     ` Henning Hraban Ramm [this message]
2024-01-22 12:04                       ` Thomas Meyer
2024-01-22 19:24                         ` Wolfgang Schuster
2024-01-23 10:39                           ` Thomas Meyer
2024-01-18 12:51             ` [NTG-context] Re: context version 20240118 (was: "Registerhaltigkeit") luigi scarso
2024-01-18 14:01               ` [NTG-context] Re: context version 20240118 Thomas Meyer

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=43c6f5d3-188f-47cb-93d6-e043a93b74fd@fiee.net \
    --to=texml@fiee.net \
    --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).