What are \usepath and \usesubpath supposed to do? I looked into the mkiv-code but could not find an explanation. I have a problem finding files from within a project-product-component structure and I hoped to solve through these macros. Sofar without success. In the wiki there is an item on project structure containing a \usepath but that didn't help me out. Hans van der Meer
Am 29.09.2011 um 17:18 schrieb Meer, H. van der:
What are \usepath and \usesubpath supposed to do? I looked into the mkiv-code but could not find an explanation. I have a problem finding files from within a project-product-component structure and I hoped to solve through these macros. Sofar without success. In the wiki there is an item on project structure containing a \usepath but that didn't help me out.
You can specify with them subdirectories where context looks when you include a component file, e.g. instead of \startproduct product \component subdirectory/component-1 \component subdirectory/component-2 \stopproduct you can write \startproduct product \usepath[subdirectory] \component component-1 \component component-2 \stopproduct Wolfgang
This didn't work for me. I guess it has to do with some misunderstanding about the directory from where projects start reckoning. The directory structure is: directory-project directory-project/product (context runs from here) directory-project/product/component-a-subfiles directory-project/product/component-b-subfiles Code in directory-project/product/component-a-subfile does \input but cannot find files in directories below or in directories alongside. My question is "from what directory starts the search tree? Hans van der Meer On 29 sep. 2011, at 17:23, Wolfgang Schuster wrote:
Am 29.09.2011 um 17:18 schrieb Meer, H. van der:
What are \usepath and \usesubpath supposed to do? I looked into the mkiv-code but could not find an explanation. I have a problem finding files from within a project-product-component structure and I hoped to solve through these macros. Sofar without success. In the wiki there is an item on project structure containing a \usepath but that didn't help me out.
You can specify with them subdirectories where context looks when you include a component file, e.g. instead of
\startproduct product
\component subdirectory/component-1 \component subdirectory/component-2
\stopproduct
you can write
\startproduct product
\usepath[subdirectory]
\component component-1 \component component-2
\stopproduct
Wolfgang
Am 29.09.2011 um 18:54 schrieb Meer, H. van der:
This didn't work for me. I guess it has to do with some misunderstanding about the directory from where projects start reckoning. The directory structure is:
directory-project directory-project/product (context runs from here) directory-project/product/component-a-subfiles directory-project/product/component-b-subfiles
Code in directory-project/product/component-a-subfile does \input but cannot find files in directories below or in directories alongside. My question is "from what directory starts the search tree?
When you process the product it starts from the directory where the product is (directory-project/product) and when you process a component it starts from the directory where the component files is (“directory-project/product/component-a-subfiles” or “directory-project/product/component-b-subfiles”). You problem could be that you use \input to load the components but you need the \component command. Wolfgang
Am 29.09.2011 um 17:18 schrieb Meer, H. van der:
What are \usepath and \usesubpath supposed to do? I looked into the mkiv-code but could not find an explanation.
It’s sometimes easier to look at the definition of the MkII version of the command to understand how something works. Wolfgang
participants (2)
-
Meer, H. van der -
Wolfgang Schuster