[NTG-context] arguments to ctxlua

2010-03-30 Thread Hans van der Meer
When I have a Lua function with 2 arguments: \startluacode function f(a,b) ... \stopluacode called through: \def\callf#1#2{\ctxlua{f(#1,#2)}} and do this actually with one argument: \callf{one} then I find that the absent argument b in f(a,b) is

Re: [NTG-context] arguments to ctxlua

2010-03-30 Thread Hans Hagen
On 30-3-2010 19:45, Hans van der Meer wrote: When I have a Lua function with 2 arguments: \startluacode function f(a,b) ... \stopluacode called through: \def\callf#1#2{\ctxlua{f(#1,#2)}} and do this actually with one argument: \callf{one} so, #1 will be one and #2 will be the next token

Re: [NTG-context] arguments to ctxlua

2010-03-30 Thread Peter M√ľnster
On Tue, Mar 30 2010, Hans van der Meer wrote: called through: \def\callf#1#2{\ctxlua{f(#1,#2)}} and do this actually with one argument: \callf{one} then I find that the absent argument b in f(a,b) is not nil but a string of length 1. Hello Hans, You want probably something