From: Pablo Rodriguez via ntg-context <ntg-context@ntg.nl>
To: Rik Kabel via ntg-context <ntg-context@ntg.nl>
Cc: Pablo Rodriguez <oinos@gmx.es>
Subject: Re: xtables regression with LMTX 2022-12-21
Date: Thu, 22 Dec 2022 22:19:33 +0100 [thread overview]
Message-ID: <5b126731-645b-5430-ef50-c0b2706766d7@gmx.es> (raw)
In-Reply-To: <c0bc3d9a-7e86-4f54-c8eb-710ad2723ad7@rik.users.panix.com>
On 12/22/22 21:14, Rik Kabel via ntg-context wrote:
> With the latest (2022-12-21) LMTX I see a regression in xtables. The
> following code:
> […]
> The problem appears to be LMTX-specific. (I did not save 2022-12-15 for
> testing, but did not see the problem with that version.)
Hi Rik,
I can confirm that the regression only arises in LMTX and in current
latest. With LMTX from 2022.12.15 18:12, the xtable is fine.
It seems to be related to the replacement of \newdimen and \newcount
with \newdimension and \newinteger (which Hans mentioned in
https://mailman.ntg.nl/pipermail/ntg-context/2022/107452.html).
Just in case it helps,
Pablo
___________________________________________________________________________________
If your question is of interest to others as well, please add an entry to the Wiki!
maillist : ntg-context@ntg.nl / https://www.ntg.nl/mailman/listinfo/ntg-context
webpage : https://www.pragma-ade.nl / http://context.aanhet.net
archive : https://bitbucket.org/phg/context-mirror/commits/
wiki : https://contextgarden.net
___________________________________________________________________________________
next prev parent reply other threads:[~2022-12-22 21:19 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-12-22 20:14 Rik Kabel via ntg-context
2022-12-22 21:19 ` Pablo Rodriguez via ntg-context [this message]
2022-12-22 21:31 ` Hans Hagen via ntg-context
2022-12-22 21:30 ` Hans Hagen via ntg-context
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=5b126731-645b-5430-ef50-c0b2706766d7@gmx.es \
--to=ntg-context@ntg.nl \
--cc=oinos@gmx.es \
/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).