[NTG-context] Re: unprotecting when defining in Lua

2024-04-29 Thread Pablo Rodriguez via ntg-context
On 4/29/24 19:32, Wolfgang Schuster wrote: > Pablo Rodriguez via ntg-context schrieb am 29.04.2024 um 18:21: >> Is \protected the same as \unexpanded? > > Yes they are the same (\protected is the primitive and \unexpanded is a > copy) but this wasn't always the case. > > Original TeX didn't

[NTG-context] Re: unprotecting when defining in Lua

2024-04-29 Thread Wolfgang Schuster
Pablo Rodriguez via ntg-context schrieb am 29.04.2024 um 18:21: On 4/29/24 18:04, Wolfgang Schuster wrote: Pablo Rodriguez via ntg-context schrieb am 29.04.2024 um 17:22: [...] Which is the right way to use "interfaces.definecommand" to get a simple command as in standard TeX? I mean, no a

[NTG-context] Re: unprotecting when defining in Lua

2024-04-29 Thread Pablo Rodriguez via ntg-context
On 4/29/24 18:04, Wolfgang Schuster wrote: > Pablo Rodriguez via ntg-context schrieb am 29.04.2024 um 17:22: >> [...] >> Which is the right way to use "interfaces.definecommand" to get a simple >> command as in standard TeX? >> >> I mean, no a non \permanent or non \protected command. > > You

[NTG-context] Re: unprotecting when defining in Lua

2024-04-29 Thread Wolfgang Schuster
Pablo Rodriguez via ntg-context schrieb am 29.04.2024 um 17:22: Dear list, I have the following sample: \starttext \startluacode function document.test(str) context(str) end interfaces.definecommand { name = "testing", protected = false, macro