ntg-context - mailing list for ConTeXt users
 help / color / mirror / Atom feed
* set_lua freezes control sequences
@ 2020-08-25 13:59 Marcel Fabian Krüger
  2020-08-25 14:48 ` Hans Hagen
  0 siblings, 1 reply; 3+ messages in thread
From: Marcel Fabian Krüger @ 2020-08-25 13:59 UTC (permalink / raw)
  To: ConTeXt users list

Hi,

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.

Best regards,
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
___________________________________________________________________________________

^ permalink raw reply	[flat|nested] 3+ messages in thread

* Re: set_lua freezes control sequences
  2020-08-25 13:59 set_lua freezes control sequences Marcel Fabian Krüger
@ 2020-08-25 14:48 ` Hans Hagen
  2020-08-25 18:28   ` Marcel Fabian Krüger
  0 siblings, 1 reply; 3+ messages in thread
From: Hans Hagen @ 2020-08-25 14:48 UTC (permalink / raw)
  To: mailing list for ConTeXt users

On 8/25/2020 3:59 PM, Marcel Fabian Krüger wrote:
> Hi,
> 
> 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).

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 / 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
___________________________________________________________________________________

^ permalink raw reply	[flat|nested] 3+ messages in thread

* Re: set_lua freezes control sequences
  2020-08-25 14:48 ` Hans Hagen
@ 2020-08-25 18:28   ` Marcel Fabian Krüger
  0 siblings, 0 replies; 3+ messages in thread
From: Marcel Fabian Krüger @ 2020-08-25 18:28 UTC (permalink / raw)
  To: ConTeXt users list

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
___________________________________________________________________________________

^ permalink raw reply	[flat|nested] 3+ messages in thread

end of thread, other threads:[~2020-08-25 18:28 UTC | newest]

Thread overview: 3+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2020-08-25 13:59 set_lua freezes control sequences Marcel Fabian Krüger
2020-08-25 14:48 ` Hans Hagen
2020-08-25 18:28   ` Marcel Fabian Krüger

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).