From: Jaroslav Hajtmar <hajtmar@gyza.cz>
Cc: mailing list for ConTeXt users <ntg-context@ntg.nl>
Subject: Re: Optimal way to defining of macros in Luacode in ConTeXt
Date: Thu, 14 Jul 2011 17:12:28 +0200 [thread overview]
Message-ID: <4E1F075C.1010405@gyza.cz> (raw)
In-Reply-To: <21109B35-0FFC-44B7-817B-9601A6D5101A@googlemail.com>
Thanx very much Hans and Wolfgang too,
I converted ALL my ConTeXt definitions (macros) with fixed numbers of
parameters by using yours method - ie:
interfaces.definecommand {
name = "....",
macro = .....,
arguments = {
{ "content", "string" },
{ "content", "string" },
},
}
It is great and very easy - thanx.
Now I want convert rest of definitions (macros) - they have varied
numbers of parameters.
Is there any similar way to do it? Suffice it to indicate how.
Thanx Jaroslav
To show what macros I want to convert, I mention these examples:
\def\opencsvfile{%
\dosingleempty\doopencsvfile%
}
\def\doopencsvfile[#1]{%
\dosinglegroupempty\dodoopencsvfile
}
\def\dodoopencsvfile#1{%
\iffirstargument
\ctxlua{thirddata.scancsv.opencsvfile("#1")}
\else
\ctxlua{thirddata.scancsv.opencsvfile()}
\fi
}
or other macro etc:
% \doloopaction % implicit use \lineaction macro
% \doloopaction{\action} % use \action macro for all lines
% \doloopaction{\action}{4} % use \action macro for first 4 lines
% \doloopaction{\action}{2}{5} % use \action macro for lines from 2 to 5
\def\doloopaction{\dotriplegroupempty\doloopAction}
\def\doloopAction#1#2#3{%
\opencsvfile%
\doifsomethingelse{#3}{%3 args.
\doloopfromto{#2}{#3}{#1}% if 3 arguments then do #1 macro from #2
line to #3 line
}{%
\doifsomethingelse{#2}{%2 args.
\doloopfromto{1}{#2}{#1}% if 2 arguments then do #1 macro for first
#2 lines
}%
{\doifsomethingelse{#1}{% 1 arg.
\doloopfromto{-1}{-1}{#1}%
}{% if without arguments then do \lineaction macro for all lines
\doloopfromto{-1}{-1}{\lineaction}%
}%
}%
}%
}%
Dne 13.7.2011 16:33, Wolfgang Schuster napsal(a):
> Am 13.07.2011 um 16:09 schrieb Jaroslav Hajtmar:
>
>
>> Thanx Wolfgang,
>>
>> It looks very interesting... It can be used this method for example for macro definitions?
>>
> It depends what you want to achieve, while you try to create many commands
> in the form \MacroXXX where each command contains some content i define
> only one command which takes the content only when requested.
>
>
>> When I will return to the subject of this mail:
>> Can also be used for the council said Hans macros with multiple parameters?
>>
>> For example macros without parameter is no problem:
>> context.setvalue('printline',calling.luafunction(),tex.par)
>> I assume that for a more parameters cannot be used context.setvalue (...) ..
>>
>> But how to use multiple parameters when defining the macro as follows:
>> context([[\\def\\paramcontrol#1#2{%s}]],thirddata.scancsv.paramcontrol('#1', '#2'))
>>
> Look into cldf-int.lua where you can see a method to create TeX commands
> without optional arguments from Lua.
>
> Wolfgang
>
___________________________________________________________________________________
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://tex.aanhet.net
archive : http://foundry.supelec.fr/projects/contextrev/
wiki : http://contextgarden.net
___________________________________________________________________________________
next prev parent reply other threads:[~2011-07-14 15:12 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-07-12 15:30 Jaroslav Hajtmar
2011-07-12 15:43 ` Hans Hagen
2011-07-13 8:05 ` Jaroslav Hajtmar
2011-07-13 9:55 ` Hans Hagen
2011-07-13 10:05 ` Jaroslav Hajtmar
2011-07-13 12:56 ` Wolfgang Schuster
2011-07-13 14:09 ` Jaroslav Hajtmar
2011-07-13 14:33 ` Wolfgang Schuster
2011-07-14 15:12 ` Jaroslav Hajtmar [this message]
2011-07-14 15:28 ` Hans Hagen
2011-07-13 18:05 ` Hans Hagen
2011-07-12 15:50 ` Wolfgang Schuster
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=4E1F075C.1010405@gyza.cz \
--to=hajtmar@gyza.cz \
--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).