Am 16.12.22 um 10:09 schrieb Pawel Urbanski via ntg-context:

When I compile a document I switch to the SubSubFolder for the document file is in there.

In my experience this won’t work. ConTeXt searches from the current folder (you can configure search paths, but I gave up on that, and you’d have to do it in the called file). It should be enough to call the environment from the project, but either the project or the environment isn’t found if the path doesn’t fit the call location. Hraban

Another think you might want to consider: automatic local overrides. So, I’d copy everthing to a build folder, copy the environment from somewhere above unless the current folder contains a file with the same name. Denis Von: ntg-context Im Auftrag von Pawel Urbanski via ntg-context Gesendet: Freitag, 16. Dezember 2022 11:01 An: mailing list for ConTeXt users Cc: Pawel Urbanski Betreff: Re: [NTG-context] Project structure with nested subfolders and shared environments. Thank you for responses. While the ability to sort of inherit setups would be very useful it looks like as of time of posting this message in December 2022 it is not possible. As a workaround I will create a shead environment file and just bulk copy it to subfolders. In case when I'll need to globally change some configuration I can just replace the file. I keep all my documents in GIT so the ability to reverte hte change is just a command away. Thanks for help. Best, Pawel On Fri, Dec 16, 2022 at 10:55 AM Henning Hraban Ramm via ntg-context mailto:ntg-context@ntg.nl> wrote: Am 16.12.22 um 10:09 schrieb Pawel Urbanski via ntg-context:

When I compile a document I switch to the SubSubFolder for the document file is in there.

In my experience this won’t work. ConTeXt searches from the current folder (you can configure search paths, but I gave up on that, and you’d have to do it in the called file). It should be enough to call the environment from the project, but either the project or the environment isn’t found if the path doesn’t fit the call location. Hraban ___________________________________________________________________________________ If your question is of interest to others as well, please add an entry to the Wiki! maillist : ntg-context@ntg.nlmailto:ntg-context@ntg.nl / https://www.ntg.nl/mailman/listinfo/ntg-context webpage : https://www.pragma-ade.nl / http://context.aanhet.net archive : https://bitbucket.org/phg/context-mirror/commits/ wiki : https://contextgarden.net ___________________________________________________________________________________

Also, I think you'll need to load the environment in your products as well. I don't think linking to the project is enough. (Check the mailing list, I have also asked similar questions already...) Best, Denis

-----Ursprüngliche Nachricht----- Von: ntg-context Im Auftrag von Henning Hraban Ramm via ntg-context Gesendet: Freitag, 16. Dezember 2022 07:52 An: Pawel Urbanski via ntg-context Cc: Henning Hraban Ramm Betreff: Re: [NTG-context] Project structure with nested subfolders and shared environments.

Am 15.12.22 um 22:52 schrieb Pawel Urbanski via ntg-context:

...

\usepath [{ Metadata }]

Did you try without the spaces? I’d assume ConTeXt will look for a folder " Metadata " and not "Metadata". If this is just a template variable, you didn’t tell us about templating.

And then it matters from where you call your files (MainFolder, SubFolder or whereever).

Hraban ________________________________________________________________ ___________________ If your question is of interest to others as well, please add an entry to the Wiki!

maillist : ntg-context@ntg.nl / https://www.ntg.nl/mailman/listinfo/ntg- context webpage : https://www.pragma-ade.nl / http://context.aanhet.net archive : https://bitbucket.org/phg/context-mirror/commits/ wiki : https://contextgarden.net ________________________________________________________________ ___________________