From: Romain Diss <romain.diss@yahoo.fr>
To: mailing list for ConTeXt users <ntg-context@ntg.nl>
Subject: Reading product environment within a component file
Date: Sun, 2 Dec 2012 22:56:02 +0100 [thread overview]
Message-ID: <201212022256.03363.romain.diss@yahoo.fr> (raw)
Hi all,
Since I read the thread concerning the LaTeX \includeonly equivalent, I tried
again to make to project structure work for me (I gave up some time ago).
Here is my problem:
I have a product file p.tex
%% p.tex
\startproduct p
\environment e
\component c
\component d
\stopproduct
%% end
an environment file e.tex
%% e.tex
\startenvironment e
% style commands...
\stopenvironment
%% end
and two component files c.tex and d.tex
%% c.tex (d.tex is the same file, except content part)
\setupreferencing[autofile=yes]
\setupinteraction[state=start]
\startcomponent c
\product p
% content
\stopcomponent
but no project file.
When I run context on the product file, everything is ok. But when I run
context on one component file, it doesn't read the environment file because
the \product command doesn't seem to be read (that's what I understand from
the documentation). So, how should I do to inform context to read the
environment mentionned in the product file. Is it obligatory to use a project
file to be able to read the parent environment when processing a component?
Another question which I think is linked to the previous one is: is one
supposed to run context on a component? My different tests shows that a run on
a component load all the other components mentionned in the product. So it
seems to be equivalent to run context on a product or on a component (except
for the environment problem mentionned before). That's also what the wiki
seems to say (http://wiki.contextgarden.net/Project_structure):
"In addition, you have to keep in mind that when compiling a product or
component file, ConTeXt goes "up" to the project file and compiles everything
it finds in there that is not a \product".
So, actually, I'm not able to reproduce the \includeonly equivalent with
\component (even if I use \setupreferencing[autofile=yes] and
\setupinteraction[state=start]).
Do I miss something?
All the best.
--
Romain Diss
<romain.diss@yahoo.fr>
___________________________________________________________________________________
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
___________________________________________________________________________________
reply other threads:[~2012-12-02 21:56 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=201212022256.03363.romain.diss@yahoo.fr \
--to=romain.diss@yahoo.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).