From: "Marcel Fabian Krüger" <tex@2krueger.de>
To: Hans Hagen <j.hagen@xs4all.nl>
Cc: mailing list for ConTeXt users <ntg-context@ntg.nl>
Subject: Re: Changed behavior of ^^ in csname
Date: Thu, 11 Jun 2020 22:47:53 +0200 [thread overview]
Message-ID: <20200611204753.rkdnvshxtjydnfmf@yoga> (raw)
In-Reply-To: <de06a8d1-b911-4059-36ae-869e6d722c18@xs4all.nl>
On Thu, Jun 11, 2020 at 07:51:56PM +0200, Hans Hagen wrote:
> On 6/11/2020 12:24 PM, Marcel Fabian Krüger wrote:
>
> > shows exactly the same behavior.
> Looks like i don't catch the case where a cs is constructed, so i'll add
> some checking there too (it is tempting to remove all that ^^ stuff).
Thanks. I think "the ^^ stuff" is actually quite useful, especially when
debugging international documents. Especially when the glyphs come from
a language you are not used to, it is quite nice to just have a hex
representation without needing pecial editors and ^^ is the only way to get
that without introducing actual changes to behavior.
I had another issue with the latest luametatex:
The following document:
\starttext
\def\mymacro#1 bc{}
{\mymacro a b bc}
\stoptext
used to work and lead to no output. But in the new luametatex version,
it complains about "! Argument of \mymacro has an extra }" as if it
doesn't see the " bc" argument delimiter.
Marcel
>
> Hans
___________________________________________________________________________________
If your question is of interest to others as well, please add an entry to the Wiki!
maillist : ntg-context@ntg.nl / http://www.ntg.nl/mailman/listinfo/ntg-context
webpage : http://www.pragma-ade.nl / http://context.aanhet.net
archive : https://bitbucket.org/phg/context-mirror/commits/
wiki : http://contextgarden.net
___________________________________________________________________________________
next prev parent reply other threads:[~2020-06-11 20:47 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-06-11 2:06 Marcel Fabian Krüger
2020-06-11 8:07 ` Hans Hagen
2020-06-11 10:24 ` Marcel Fabian Krüger
2020-06-11 17:51 ` Hans Hagen
2020-06-11 20:47 ` Marcel Fabian Krüger [this message]
2020-06-12 6:04 ` Hans Hagen
2020-06-12 18:05 ` Marcel Fabian Krüger
[not found] ` <20200615121737.ytepj47mtvmcujy4@yoga>
[not found] ` <98372899-4f2e-447b-c9f1-29c80fcec13d@xs4all.nl>
[not found] ` <20200617101059.3zvwgt5qltufl64v@yoga>
2020-06-17 13:43 ` Yet another cornercase of ^^ handling in LuaMetaTeX Hans Hagen
2020-06-17 14:24 ` Marcel Fabian Krüger
2020-06-17 16:12 ` Hans Hagen
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=20200611204753.rkdnvshxtjydnfmf@yoga \
--to=tex@2krueger.de \
--cc=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).