From: "Marcel Fabian Krüger" <tex@2krueger.de>
To: ConTeXt users list <ntg-context@ntg.nl>
Subject: Re: set_lua freezes control sequences
Date: Tue, 25 Aug 2020 20:28:53 +0200 [thread overview]
Message-ID: <20200825182853.unx732u2oq6hw3q4@yoga> (raw)
In-Reply-To: <3424783c-9c8f-3235-75b4-0d1e4e15b71d@xs4all.nl>
On Tue, Aug 25, 2020 at 04:48:27PM +0200, Hans Hagen wrote:
> > I noticed that recent LuaMetaTeX versions treats control sequences
> > defined using token.set_lua with `value` or `condition` as frozen and
> > does not allow redefining them. Given that these are not macros, we also
> > can't "unfreeze" them using \unletfrozen.
> >
> > 1. Would it be possible to add a variant of Lua value and condition
> > control sequences that are not frozen?
> >
> > 2. Also is there some way to disable the \frozen restrictions
> > altogether? Maybe \suppressfrozenerror?
> >
> > 3. I also noticed that `token.set_lua` is not affected by control
> > sequences being frozen. Therefore it allows redefining frozen
> > control sequences which seems inconsistent.
> It's all on purpose. Btw, these mechanisms are very experimental (and
> undocumented and might to evolve).
I know, but they are fun to play with. Especially the `value`
kind was one of the most important things I always missed in LuaTeX.
Marcel
___________________________________________________________________________________
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
___________________________________________________________________________________
prev parent reply other threads:[~2020-08-25 18:28 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-08-25 13:59 Marcel Fabian Krüger
2020-08-25 14:48 ` Hans Hagen
2020-08-25 18:28 ` Marcel Fabian Krüger [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=20200825182853.unx732u2oq6hw3q4@yoga \
--to=tex@2krueger.de \
--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).