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