From: Hans Hagen <pragma@wxs.nl>
To: mailing list for ConTeXt users <ntg-context@ntg.nl>
Subject: Re: setting variable on cmd-line
Date: Mon, 21 Sep 2009 10:05:29 +0200 [thread overview]
Message-ID: <4AB733C9.3050805@wxs.nl> (raw)
In-Reply-To: <alpine.LNX.2.00.0909210809080.17120@gaston.couberia.bzh>
Peter Münster wrote:
> On Mon, 21 Sep 2009, luigi scarso wrote:
>
>>>>> test-file:
>>>>>
>>>>> \starttext
>>>>> Value of myVar: \ctxlua{tex.print(document.arguments["arguments=myVar"])}
>>>>> \stoptext
>>>>>
>>>>> cmd-line:
>>>>>
>>>>> context --arguments=myVar=myValue test
>>>>>
>>>>> But this syntax is very strange!
>>>> Does
>>>> context --arguments="myVar=myValue" test
>>>> work too ?
>>> Yes, I'm using bash, so --arguments="myVar=myValue" is the same as
>>> --arguments=myVar=myValue
>>>
>>> That means, context does not see the quotes.
>> OK, in this way syntax looks less strange
>
> It's not the syntax of the cmd-line that looks strange, it's the syntax how
> to get the value of the variable:
> \ctxlua{tex.print(document.arguments["arguments=myVar"])}
>
> I'm quite sure, that this is not Hans' intention.
>
> As I've written yesterday, I suppose, that the following syntax is wanted:
> \getvariable{environment}{myVar} but this does not work...
>
how does it look with:
local flag, value = argument:match("^%-+(.-)=(.-)$")
.+ -> .-
-----------------------------------------------------------------
Hans Hagen | PRAGMA ADE
Ridderstraat 27 | 8061 GH Hasselt | The Netherlands
tel: 038 477 53 69 | fax: 038 477 53 74 | www.pragma-ade.com
| 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://tex.aanhet.net
archive : https://foundry.supelec.fr/projects/contextrev/
wiki : http://contextgarden.net
___________________________________________________________________________________
next prev parent reply other threads:[~2009-09-21 8:05 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-09-18 13:31 Peter Münster
2009-09-20 19:46 ` Peter Münster
2009-09-20 21:24 ` luigi scarso
2009-09-21 5:39 ` Peter Münster
2009-09-21 5:52 ` luigi scarso
2009-09-21 6:16 ` Peter Münster
2009-09-21 8:05 ` Hans Hagen [this message]
2009-09-21 19:43 ` Peter Münster
2009-09-21 20:23 ` Hans Hagen
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=4AB733C9.3050805@wxs.nl \
--to=pragma@wxs.nl \
--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).