From: Hans Hagen <pragma@wxs.nl>
To: ntg-context@ntg.nl
Subject: Re: Product-component structure
Date: Sat, 25 Jun 2016 11:56:03 +0200 [thread overview]
Message-ID: <24241387-a8a7-0b45-62a7-574bb31cb419@wxs.nl> (raw)
In-Reply-To: <alpine.OSX.2.02.1606250441110.21232@nqv-znpobbx>
On 6/25/2016 10:42 AM, Aditya Mahajan wrote:
> On Sat, 25 Jun 2016, Wolfgang Schuster wrote:
>
>>> Aditya Mahajan <mailto:adityam@umich.edu>
>>> 24. Juni 2016 um 21:19
>>> Hi,
>>>
>>> This is based on a question on tex.sx:
>>> http://tex.stackexchange.com/q/316504/323
>>>
>>> In file-job.lua, we have:
>>>
>>> local processors = utilities.storage.allocate {
>>> ...
>>> [v_product] = {
>>> [v_text] = { "many", processfilemany },
>>> [v_project] = { "once", processfileonce },
>>> [v_environment] = { "once", processfileonce },
>>> [v_product] = { "many", processfilemany },
>>> [v_component] = { "many", processfilemany },
>>> },
>>> [v_component] = {
>>> [v_text] = { "many", processfilemany },
>>> [v_project] = { "once", processfileonce },
>>> [v_environment] = { "once", processfileonce },
>>> [v_product] = { "none", processfilenone },
>>> [v_component] = { "many", processfilemany },
>>> }
>>> }
>>>
>>> Then, why is the product file processed multiple times?
>> The rules for a component files are applied *after* \startcomponent
>> which isn’t the case for the example where in the first iteration
>> the "text" rules are applied and in the following iteration the rules
>> for a product file.
>>
>> Moving \product … after \startcomponent prevents the loop but
>> the environment won’t be loaded anymore because the product
>> file isn’t loaded anymore.
>
> So, what's the recommended alternative? One could move the \environment
> to the components, but that can lead to a lot of repetitions (if there
> are many environments).
i always use one main environment (that can include others) and putting
an \environment on top of a component is then not much overhead
(compared to getting the content done)
Hans
--
-----------------------------------------------------------------
Hans Hagen | PRAGMA ADE
Ridderstraat 27 | 8061 GH Hasselt | The Netherlands
tel: 038 477 53 69 | 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 : http://foundry.supelec.fr/projects/contextrev/
wiki : http://contextgarden.net
___________________________________________________________________________________
next prev parent reply other threads:[~2016-06-25 9:56 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-06-24 19:19 Aditya Mahajan
2016-06-24 22:20 ` Hans Hagen
2016-06-25 6:25 ` Wolfgang Schuster
2016-06-25 8:42 ` Aditya Mahajan
2016-06-25 9:56 ` Hans Hagen [this message]
2016-06-25 16:37 ` Aditya Mahajan
2016-06-25 17:10 ` Wolfgang Schuster
2016-06-25 17:24 ` Aditya Mahajan
2016-06-25 17:13 ` Wolfgang Schuster
2016-06-25 17:25 ` Aditya Mahajan
2016-07-11 11:01 ` Procházka Lukáš Ing.
2016-07-11 14:42 ` Alan BRASLAU
2016-06-26 9:34 ` 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=24241387-a8a7-0b45-62a7-574bb31cb419@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).