From: louis.ad@hotmail.ch
To: ntg-context@ntg.nl
Subject: [NTG-context] Expected behaviour of \definelayout
Date: Tue, 05 Nov 2024 17:15:30 -0000 [thread overview]
Message-ID: <173082693060.1601628.16677952919182338112@cgl.ntg.nl> (raw)
Hello,
I am new to ConTeXt and was trying to understand whether the following behaviour of \definelayout is expected.
Consider this example,
> \setuplayout[grid=yes]
> \showgrid
> \definelayout[odd][
> backspace=50mm,
> width=90mm,
> topspace=20mm,
> header=0mm,
> footer=0mm,
> height=250mm,
> ]
>
> \starttext
> \showframe
> \dorecurse{10}{\input knuth }
> \stoptext
which I compile with `context example.tex` (ConTeXt Process Management 1.06, current version: 2024.02.27 09:18, obtained via TeXLive 2024).
While the document's layout updates on page 2 (at least, what's being shown by \showframe), the text is typeset using the previous (page 1) layout until it encounters the next \par.
This repeats on the transition from page 2 to 3.
I have tried to look for an answer in the following texts to no avail,
- The layout guide: "It's in the details"
- The "ConTEXt Mark IV: an excursion"
- The mailing list: Peter Hopcroft chimed in with a similar issue in Dec 2022 (which I did not manage to replicate; it appears the solution was to enforce paragraphs at the layout change?)
Is this just the expected behaviour of the layout engine or am I missing something in my preamble?
I would very much appreciate your insights, thank you in advance!
Louis
___________________________________________________________________________________
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-11-05 17:19 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=173082693060.1601628.16677952919182338112@cgl.ntg.nl \
--to=louis.ad@hotmail.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).