On 3/6/2015 9:22 AM, Procházka Lukáš Ing. - Pontex s. r. o. wrote:
Hello,
when you want to use your personal (additional) path (but apparently not a tree), e.g. for styles (environments), you can use --path switch:
" context.exe --path=c:\MyDirectory\MyContextStyles MyFile.tex "
(Source: "context.exe --help")
(Once I tried also:
" set TeXMFLocal=c:\MyName\MyContextStyles & context.exe MyFile.tex "
but ConTeXt doesn't look for TeXMFLocal nor TeXMF-Local environment paths, as I believed.)
I didn't test whether "--path=c:\MyDirectory\MyContextStyles/" or "--path=c:\MyDirectory\MyContextStyles//" or "--path=c:\MyDirectory\MyContextStyles/*" or "--path=c:\MyDirectory\MyContextStyles/**" causes Ctx to use the whole tree instead of one path.
why should it ... a path is a path unless specified otherwise we have a runtime tree search with: context --path=tree://e:/tmp/whatever/**/ --global somefile.tex which is quite ok for jobs that involve not that many files and a cached-across-jobs search with context --path=dirfile://e:/tmp/whatever --global somefile.tex (in that case you need to delete dirlist.tuc in the given path when you add or remove files) the second one we use here in automated runs on servers where books are generated from thousands of small files sitting on an nfs share and this speeds up the search the --global bypasses the check for a valid file Hans ----------------------------------------------------------------- Hans Hagen | PRAGMA ADE Ridderstraat 27 | 8061 GH Hasselt | The Netherlands tel: 038 477 53 69 | voip: 087 875 68 74 | www.pragma-ade.com | www.pragma-pod.nl -----------------------------------------------------------------