From: Hans Hagen <j.hagen@xs4all.nl>
To: ntg-context@ntg.nl
Subject: [NTG-context] Re: Why the way key-value argument is called affected the document's output?
Date: Mon, 8 Jan 2024 23:16:27 +0100 [thread overview]
Message-ID: <783d0576-1441-4235-bdc7-f02432bec379@xs4all.nl> (raw)
In-Reply-To: <170475151639.1645.1665703741655488372@cgl.ntg.nl>
On 1/8/2024 11:05 PM, 111414w@gmail.com wrote:
> Hi,
>
> I was cleaning and formatting my context file and then when I compiled it, the output I got introduced extra vertical spacings at the section headings that weren't there in the previous compilations. I had to spend enormous amount of time trying to fix it so to emulate my previous outputs. Turns out the problem was how I called one of the key-value argument in the document.
>
> I really wanna know the reason why it did influenced the output?
>
> Provided below is the minimal source code (and it is producing different outputs, meaning the vertical spacings are not same, on my device running the version released in the September and also tested with the latest release.)
>
>
> """
> %% differences in outputs, for how "grid=yes" is called.
>
> %% Type 1.
> %\setuplayout[grid=yes]
Here you set the grid variable to "yes".
> %% Type 2.
> %\setuplayout[
> %grid=yes
> %]
Here you set the grid variable to "yes " so a trailing space.
> \setuphead[section][grid=low] %% needed to observe the output difference
> \starttext
>
> \title{Alpha}
> \subsection{Beta}
> \input{knuth}
>
> \stoptext
So this is ok:
\setupfoo
[a=A,
b=B]
\setupfoo
[a=A,
b=B,
]
I'm not aware of funmdamental changes in the parse, apart from that in
many setup commands one can now do this:
\setupfoo
[A=\this[works],
B=\that[doestoo]]
as nested brackets are handled.
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 / 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
___________________________________________________________________________________
next prev parent reply other threads:[~2024-01-08 22:20 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-01-08 22:05 [NTG-context] " 111414w
2024-01-08 22:16 ` Hans Hagen [this message]
2024-01-08 22:33 ` [NTG-context] " Ali Ali
2024-01-08 22:40 ` Wolfgang Schuster
2024-01-08 22:53 ` Ali Ali
2024-01-13 16:39 ` 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=783d0576-1441-4235-bdc7-f02432bec379@xs4all.nl \
--to=j.hagen@xs4all.nl \
--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).