From: Hans Hagen <j.hagen@xs4all.nl>
To: mailing list for ConTeXt users <ntg-context@ntg.nl>,
Gerben Wierda <gerben.wierda@rna.nl>
Subject: Re: Using command line values in a TeX document; writing a script?
Date: Tue, 14 Apr 2020 12:05:48 +0200 [thread overview]
Message-ID: <48215896-61fa-49f5-c991-864bf3725c39@xs4all.nl> (raw)
In-Reply-To: <21EE30E7-D8C9-4797-8526-0BBC23AB68E2@rna.nl>
On 4/14/2020 11:25 AM, Gerben Wierda wrote:
> This helps for adding information to my processing.
>
> What I was also looking for is that I don’t have a test.tex anymore, just the XML file I am parsing and a command line action.
>
> So, I use mtxrun, give it the name of an XML. lua code (using a ’script’ somewhere?) reads the XML, extracts a name (e.g. ‘foo’) from it, creates a .tex file (e.g. ‘foo.tex’), produces a .pdf file from that .tex file (e.g. ‘foo.pdf').
>
> G
>
>> On 14 Apr 2020, at 09:16, Taco Hoekwater <taco@elvenkind.com> wrote:
>>
>> Hi Gerben,
>>
>> What you want is quite easy to do since you are using lua already. Try this:
>>
>> % context --whatever=green test
>>
>> with test.tex:
>>
>> \starttext
>> \startluacode
>> table.print(environment.arguments)
>> \stopluacode
>> \stoptext
>>
>> everything from the command line ends up in environment.arguments.
\doifdocumentargument {whatever} {
... \getdocumentargument{whatever} ...
}
-----------------------------------------------------------------
Hans Hagen | PRAGMA ADE
Ridderstraat 27 | 8061 GH Hasselt | The Netherlands
tel: 038 477 53 69 | www.pragma-ade.nl | 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://context.aanhet.net
archive : https://bitbucket.org/phg/context-mirror/commits/
wiki : http://contextgarden.net
___________________________________________________________________________________
prev parent reply other threads:[~2020-04-14 10:05 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-04-13 8:29 Gerben Wierda
2020-04-14 7:16 ` Taco Hoekwater
2020-04-14 9:25 ` Gerben Wierda
2020-04-14 9:52 ` Taco Hoekwater
2020-04-15 10:19 ` Gerben Wierda
2020-04-15 11:54 ` Wolfgang Schuster
2020-04-15 12:13 ` Gerben Wierda
2020-04-15 12:43 ` r.ermers
2020-04-14 10:05 ` Hans Hagen [this message]
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=48215896-61fa-49f5-c991-864bf3725c39@xs4all.nl \
--to=j.hagen@xs4all.nl \
--cc=gerben.wierda@rna.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).