From: "Peter Münster" <pmlists@free.fr>
To: mailing list for ConTeXt users <ntg-context@ntg.nl>
Subject: Re: setting variable on cmd-line
Date: Sun, 20 Sep 2009 21:46:38 +0200 (CEST) [thread overview]
Message-ID: <alpine.LNX.2.00.0909202130420.8278@gaston.couberia.bzh> (raw)
In-Reply-To: <alpine.LNX.2.00.0909181509040.18238@gaston.couberia.bzh>
On Fri, 18 Sep 2009, Peter Münster wrote:
> I've a little feature request:
> It would be nice, to have a command line option like "--setvalue x=y" or
> similar for the "context" command to define a variable for the job.
>
> Modes are already very nice, but often I need just one value for
> conditional compiling a document instead of many binary switches.
>
> Perhaps the "context --arguments" option is what I'm looking for, but I
> didn't find how to use it.
Hello,
After reading a bit in mtx-context.lua, I've found out how to use
--arguments:
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!
This would be much nicer:
Value of myVar: \getvariable{environment}{myVar}
Perhaps there is just a bug in the evaluation of environment.arguments?
That means, instead of using the first equal sign (=) for generating the
key/value pair, the last one is used.
> Another option would be, to make the name of the result-file
> ("context --result=...") available, for example as "\resultname".
Is this the right way to go: \systemparameter{file} ?
Cheers, Peter
--
Contact information: http://pmrb.free.fr/contact/
___________________________________________________________________________________
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-20 19:46 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 [this message]
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
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=alpine.LNX.2.00.0909202130420.8278@gaston.couberia.bzh \
--to=pmlists@free.fr \
--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).