Am 28.10.24 um 13:01 schrieb Thomas A. Schmitz:

On 28.10.24 12:18, Henning Hraban Ramm wrote:

...

Hi, I’m trying to use a command line argument in parameter names – color name in the example below, variable namespace in my actual project. I guess I need more expansion, but where? Or what’s the problem here?

Perhaps my approach is too simplistic, but if I had to do something like that, I would use modes:

\startmode [fiee]   \definecolor [OEM] [c=1]   \def{OEM}{fiee} \stopmode

and for the fallback, use

\startnotallmodes [...]

then you can call from the command line with --mode=fiee and write

\color[OEM]{Company: \OEM}

But maybe your needs are more complex...

Yes, I have several arguments that I don’t want to mix into modes. In the end, I’ll need to process some files with Lua, but for the prototype I’m defining groups of variables and would like to use one of the parameters as variable namespace. I just tried to keep the example simple. Hraban

Am 28.10.24 um 16:18 schrieb Wolfgang Schuster:

Henning Hraban Ramm schrieb am 28.10.2024 um 12:18:

...

Hi, I’m trying to use a command line argument in parameter names – color name in the example below, variable namespace in my actual project. I guess I need more expansion, but where? Or what’s the problem here?

""" \setupbodyfont[plex,18pt]

% set \OEM to the parameter name, fall back to "fiee" \expanded\define\OEM{\expanded\doifelsedocumentargument{OEM} {\expanded\getdocumentargument{OEM}}{fiee}}

\doifelsedocumentargument{OEM}   {\def\OEM{\getdocumentargument{OEM}}}   {\def\OEM{fiee}}

or

\def\OEM   {\ifempty{\getdocumentargument{OEM}}%      fiee%    \else      \getdocumentargument{OEM}%    \fi}

Thank you, both works (of course, if you say so…). Also in my actual project. Can you explain why \define\OEM{\doifelsedocumentargument{OEM}{\getdocumentargument{OEM}}{fiee}} doesn’t? Hraban