Hi all,
to answer the question myself is: yes --path is the right option.
I wrote a build script that calls context inside a deep nested directory
like this:
context --path="${environmentdir}" --result=${project}.pdf ${project}.tex
The variable ${environmentdir} is created by the script.
Hi all,
in my document I have to set a long path to my environment files:
\environment ../../../hs.pub.context/env-fonts
I wonder if I can use the option --path to set hs.pub.context as input
folder to look for environment files.
But I have no idea how to pass a "list" to this option as --help
