From: Hans Hagen via ntg-context <ntg-context@ntg.nl>
To: ntg-context@ntg.nl
Cc: Hans Hagen <j.hagen@freedom.nl>
Subject: Re: \autoinsertnextspace regression / discrepancy, mkiv to lmtx
Date: Thu, 27 Oct 2022 09:54:34 +0200 [thread overview]
Message-ID: <c07a81e3-9941-18fc-994a-605fbec898d7@freedom.nl> (raw)
In-Reply-To: <05862833-a933-52a8-14d6-111885e994c2@panix.com>
On 10/26/2022 3:35 PM, Rik Kabel via ntg-context wrote:
>
> On 2022-10-26 07:43, Hans Hagen via ntg-context wrote:
>> On 10/26/2022 1:52 AM, Rik Kabel via ntg-context wrote:
>>> The following example produces different results when processed by
>>> LMTX and MkIV. In particular, a space between the X and Y is not
>>> auto-inserted by LMTX, while it is by MkIV.
>>>
>>> \starttexdefinition TEST #1
>>> #1\autoinsertnextspace
>>> \stoptexdefinition
>>> \tt
>>> \starttext
>>> \TEST{X} \emph{Y}
>>> \stoptext
>>>
>>> The MkIV result is the correct result (in my opinion).
>> more a side effect ... we lookahead and \emph is not some character
>>
>> I made a variants that does abetter job on that
>>
>> \starttexdefinition TEST #1
>> #1%
>> \autoinsertedspace % subtle name change
>> \stoptexdefinition
>>
>> but you have to wait till we update,
>>
>> Hans
>>
>>
> Thank you in advance for the upcoming fix.
>
> Can you tell us (me) why you chose to create a new macro,
> \autoinsertedspace, instead of changing the code for
> \autoinsertnextspace in LMTX? Do you see a circumstance under which the
> current LMTX behavior of \autoinsertnextspace is desirable or required?
compatibility .. it also uses a different mechanism for which that name
suits better
> Will the new macro be available under MkIV?
I suppose I can do that if needed,
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://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
___________________________________________________________________________________
prev parent reply other threads:[~2022-10-27 7:54 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-10-25 23:52 Rik Kabel via ntg-context
2022-10-26 11:43 ` Hans Hagen via ntg-context
2022-10-26 13:35 ` Rik Kabel via ntg-context
2022-10-27 7:54 ` 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=c07a81e3-9941-18fc-994a-605fbec898d7@freedom.nl \
--to=ntg-context@ntg.nl \
--cc=j.hagen@freedom.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).