Using the standalone ConTeXt, how do I add access to my texmf-local tree
I’m trying to migrate to mkiv and I’m running into a host of troubles. Here is one: publications > wrote a new auxiliary file 'prd_book.aux' This is BibTeX, Version 0.99d (TeX Live 2014) The top-level auxiliary file: prd_book.aux The style file: cont-no.bst I couldn't open database file gwierda.bib ---line 3 of file prd_book.aux : \bibdata{gwierda : } The reason is that by using this command (. /usr/local/src/ConTeXt/tex/setuptex && context test.tex) I may have the latest ConTeXt compiling test.tex (it just adds that to te front of PATH), but I’ve lost access to additions I keep in /usr/local/texlive/texmf-local and ~/Library/texmf) How do I make sure the standalone ConTeXt gets access to these? G
On 3/1/2015 11:48 AM, Gerben Wierda wrote:
I’m trying to migrate to mkiv and I’m running into a host of troubles. Here is one:
publications > wrote a new auxiliary file 'prd_book.aux' This is BibTeX, Version 0.99d (TeX Live 2014) The top-level auxiliary file: prd_book.aux The style file: cont-no.bst I couldn't open database file gwierda.bib ---line 3 of file prd_book.aux : \bibdata{gwierda : }
The reason is that by using this command
(. /usr/local/src/ConTeXt/tex/setuptex && context test.tex)
I may have the latest ConTeXt compiling test.tex (it just adds that to te front of PATH), but I’ve lost access to additions I keep in /usr/local/texlive/texmf-local and ~/Library/texmf)
How do I make sure the standalone ConTeXt gets access to these?
you can try \usemodule[oldbibtex] ----------------------------------------------------------------- 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 -----------------------------------------------------------------
On 01 Mar 2015, at 11:59, Hans Hagen
On 3/1/2015 11:48 AM, Gerben Wierda wrote:
I’m trying to migrate to mkiv and I’m running into a host of troubles. Here is one:
publications > wrote a new auxiliary file 'prd_book.aux' This is BibTeX, Version 0.99d (TeX Live 2014) The top-level auxiliary file: prd_book.aux The style file: cont-no.bst I couldn't open database file gwierda.bib ---line 3 of file prd_book.aux : \bibdata{gwierda : }
The reason is that by using this command
(. /usr/local/src/ConTeXt/tex/setuptex && context test.tex)
I may have the latest ConTeXt compiling test.tex (it just adds that to te front of PATH), but I’ve lost access to additions I keep in /usr/local/texlive/texmf-local and ~/Library/texmf)
How do I make sure the standalone ConTeXt gets access to these?
you can try \usemodule[oldbibtex]
Doesn’t change the problem. It won’t find files outside the standalone ConTeXt tree. I couldn't open database file gwierda.bib ---line 3 of file prd_book.aux : \bibdata{gwierda : } G
Am 01.03.2015 um 22:56 schrieb Gerben Wierda
: On 01 Mar 2015, at 11:59, Hans Hagen
mailto:pragma@wxs.nl> wrote: On 3/1/2015 11:48 AM, Gerben Wierda wrote:
I’m trying to migrate to mkiv and I’m running into a host of troubles. Here is one:
publications > wrote a new auxiliary file 'prd_book.aux' This is BibTeX, Version 0.99d (TeX Live 2014) The top-level auxiliary file: prd_book.aux The style file: cont-no.bst I couldn't open database file gwierda.bib ---line 3 of file prd_book.aux : \bibdata{gwierda : }
The reason is that by using this command
(. /usr/local/src/ConTeXt/tex/setuptex && context test.tex)
I may have the latest ConTeXt compiling test.tex (it just adds that to te front of PATH), but I’ve lost access to additions I keep in /usr/local/texlive/texmf-local and ~/Library/texmf)
How do I make sure the standalone ConTeXt gets access to these?
you can try \usemodule[oldbibtex]
Doesn’t change the problem. It won’t find files outside the standalone ConTeXt tree.
I couldn't open database file gwierda.bib ---line 3 of file prd_book.aux : \bibdata{gwierda : }
Where do you have your bib file? Wolfgang
On 01 Mar 2015, at 23:04, Wolfgang Schuster
Am 01.03.2015 um 22:56 schrieb Gerben Wierda
: On 01 Mar 2015, at 11:59, Hans Hagen
wrote: On 3/1/2015 11:48 AM, Gerben Wierda wrote:
I’m trying to migrate to mkiv and I’m running into a host of troubles. Here is one:
publications > wrote a new auxiliary file 'prd_book.aux' This is BibTeX, Version 0.99d (TeX Live 2014) The top-level auxiliary file: prd_book.aux The style file: cont-no.bst I couldn't open database file gwierda.bib ---line 3 of file prd_book.aux : \bibdata{gwierda : }
The reason is that by using this command
(. /usr/local/src/ConTeXt/tex/setuptex && context test.tex)
I may have the latest ConTeXt compiling test.tex (it just adds that to te front of PATH), but I’ve lost access to additions I keep in /usr/local/texlive/texmf-local and ~/Library/texmf)
How do I make sure the standalone ConTeXt gets access to these?
you can try \usemodule[oldbibtex]
Doesn’t change the problem. It won’t find files outside the standalone ConTeXt tree.
I couldn't open database file gwierda.bib ---line 3 of file prd_book.aux : \bibdata{gwierda : }
Where do you have your bib file?
~/Library/texmf
Wolfgang
___________________________________________________________________________________ If your question is of interest to others as well, please add an entry to the Wiki!
maillist : ntg-context@ntg.nl / http://www.ntg.nl/mailman/listinfo/ntg-context webpage : http://www.pragma-ade.nl / http://tex.aanhet.net archive : http://foundry.supelec.fr/projects/contextrev/ wiki : http://contextgarden.net ___________________________________________________________________________________
Am 01.03.2015 um 23:16 schrieb Gerben Wierda
: On 01 Mar 2015, at 23:04, Wolfgang Schuster
mailto:schuster.wolfgang@gmail.com> wrote: Am 01.03.2015 um 22:56 schrieb Gerben Wierda
mailto:gerben.wierda@rna.nl>: On 01 Mar 2015, at 11:59, Hans Hagen
mailto:pragma@wxs.nl> wrote: On 3/1/2015 11:48 AM, Gerben Wierda wrote:
I’m trying to migrate to mkiv and I’m running into a host of troubles. Here is one:
publications > wrote a new auxiliary file 'prd_book.aux' This is BibTeX, Version 0.99d (TeX Live 2014) The top-level auxiliary file: prd_book.aux The style file: cont-no.bst I couldn't open database file gwierda.bib ---line 3 of file prd_book.aux : \bibdata{gwierda : }
The reason is that by using this command
(. /usr/local/src/ConTeXt/tex/setuptex && context test.tex)
I may have the latest ConTeXt compiling test.tex (it just adds that to te front of PATH), but I’ve lost access to additions I keep in /usr/local/texlive/texmf-local and ~/Library/texmf)
How do I make sure the standalone ConTeXt gets access to these?
you can try \usemodule[oldbibtex]
Doesn’t change the problem. It won’t find files outside the standalone ConTeXt tree.
I couldn't open database file gwierda.bib ---line 3 of file prd_book.aux : \bibdata{gwierda : }
Where do you have your bib file?
~/Library/texmf
The minimals use ~/texmf for the local tex folder. Wolfgang
On 02 Mar 2015, at 00:15, Wolfgang Schuster
Am 01.03.2015 um 23:16 schrieb Gerben Wierda
: On 01 Mar 2015, at 23:04, Wolfgang Schuster
wrote: Am 01.03.2015 um 22:56 schrieb Gerben Wierda
: On 01 Mar 2015, at 11:59, Hans Hagen
wrote: On 3/1/2015 11:48 AM, Gerben Wierda wrote:
I’m trying to migrate to mkiv and I’m running into a host of troubles. Here is one:
publications > wrote a new auxiliary file 'prd_book.aux' This is BibTeX, Version 0.99d (TeX Live 2014) The top-level auxiliary file: prd_book.aux The style file: cont-no.bst I couldn't open database file gwierda.bib ---line 3 of file prd_book.aux : \bibdata{gwierda : }
The reason is that by using this command
(. /usr/local/src/ConTeXt/tex/setuptex && context test.tex)
I may have the latest ConTeXt compiling test.tex (it just adds that to te front of PATH), but I’ve lost access to additions I keep in /usr/local/texlive/texmf-local and ~/Library/texmf)
How do I make sure the standalone ConTeXt gets access to these?
you can try \usemodule[oldbibtex]
Doesn’t change the problem. It won’t find files outside the standalone ConTeXt tree.
I couldn't open database file gwierda.bib ---line 3 of file prd_book.aux : \bibdata{gwierda : }
Where do you have your bib file?
~/Library/texmf
The minimals use ~/texmf for the local tex folder.
Can I adapt that in some way, so I can add a few texmfs to the search path? I have no problem with adapting a file or setting an environment variable. G
Wolfgang ___________________________________________________________________________________ If your question is of interest to others as well, please add an entry to the Wiki!
maillist : ntg-context@ntg.nl / http://www.ntg.nl/mailman/listinfo/ntg-context webpage : http://www.pragma-ade.nl / http://tex.aanhet.net archive : http://foundry.supelec.fr/projects/contextrev/ wiki : http://contextgarden.net ___________________________________________________________________________________
On 3/2/2015 7:42 AM, Gerben Wierda wrote:
On 02 Mar 2015, at 00:15, Wolfgang Schuster
mailto:schuster.wolfgang@gmail.com> wrote: Am 01.03.2015 um 23:16 schrieb Gerben Wierda
mailto:gerben.wierda@rna.nl>: On 01 Mar 2015, at 23:04, Wolfgang Schuster
mailto:schuster.wolfgang@gmail.com> wrote: Am 01.03.2015 um 22:56 schrieb Gerben Wierda
mailto:gerben.wierda@rna.nl>: On 01 Mar 2015, at 11:59, Hans Hagen
mailto:pragma@wxs.nl> wrote: On 3/1/2015 11:48 AM, Gerben Wierda wrote: > I’m trying to migrate to mkiv and I’m running into a host of > troubles. > Here is one: > > publications > wrote a new auxiliary file 'prd_book.aux' > This is BibTeX, Version 0.99d (TeX Live 2014) > The top-level auxiliary file: prd_book.aux > The style file: cont-no.bst > I couldn't open database file gwierda.bib > ---line 3 of file prd_book.aux > : \bibdata{gwierda > : } > > > The reason is that by using this command > > (. /usr/local/src/ConTeXt/tex/setuptex && context test.tex) > > I may have the latest ConTeXt compiling test.tex (it just adds > that to > te front of PATH), but I’ve lost access to additions I keep in > /usr/local/texlive/texmf-local and ~/Library/texmf) > > How do I make sure the standalone ConTeXt gets access to these?
you can try \usemodule[oldbibtex]
Doesn’t change the problem. It won’t find files outside the standalone ConTeXt tree.
I couldn't open database file gwierda.bib ---line 3 of file prd_book.aux : \bibdata{gwierda : }
Where do you have your bib file?
~/Library/texmf
The minimals use ~/texmf for the local tex folder.
Can I adapt that in some way, so I can add a few texmfs to the search path? I have no problem with adapting a file or setting an environment variable.
texmfcnf.lua (can be in your texmf-local tree) or the TEXMF env var; not so different from regular texlive, only in a different configuration file -- ----------------------------------------------------------------- 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 -----------------------------------------------------------------
Am Mon, 02 Mar 2015 09:36:57 +0100 schrieb Hans Hagen:
Can I adapt that in some way, so I can add a few texmfs to the search path? I have no problem with adapting a file or setting an environment variable.
texmfcnf.lua (can be in your texmf-local tree) or the TEXMF env var; not so different from regular texlive, only in a different configuration file
I have a question regarding texmcnf.lua + TEXMCNF: On my system TEXMFCNF points to a folder where I have a special texmf.cnf that I need for texlive. This disturbs context: resolvers | resolving | looking for 'texmfcnf.lua' on weird path 'D:/texmfcnf/' from specification 'D:/texmfcnf/' and as there is not texmfcnf.lua the search pathes can't be setup. I would like to add a texmfcnf.lua there which helps context to find and load the standard configuration. What should be the content of such a texmfcnf.lua? I tried with return { type = "configuration", version = "1.", date = "2015-03-04", time = "14:00:00", comment = "ConTeXt MkIV configuration file", author = "Ulrike Fischer", content = { variables = { TEXMFCNF = {"D:/context-minimals/context/tex/texmf/web2c"} } } } but it didn't work ;-(. This doesn't setup the pathes. I also tried dofile("D:/context-minimals/context/tex/texmf/web2c/texmfcnf.lua") which didn't work either. -- Ulrike Fischer http://www.troubleshooting-tex.de/
On 3/4/2015 2:52 PM, Ulrike Fischer wrote:
Am Mon, 02 Mar 2015 09:36:57 +0100 schrieb Hans Hagen:
Can I adapt that in some way, so I can add a few texmfs to the search path? I have no problem with adapting a file or setting an environment variable.
texmfcnf.lua (can be in your texmf-local tree) or the TEXMF env var; not so different from regular texlive, only in a different configuration file
I have a question regarding texmcnf.lua + TEXMCNF:
On my system TEXMFCNF points to a folder where I have a special texmf.cnf that I need for texlive.
This disturbs context:
resolvers | resolving | looking for 'texmfcnf.lua' on weird path 'D:/texmfcnf/' from specification 'D:/texmfcnf/'
and as there is not texmfcnf.lua the search pathes can't be setup.
the weird is just reported because normally there is something texmf or web2c in the name which isn't the case there
I would like to add a texmfcnf.lua there which helps context to find and load the standard configuration. What should be the content of such a texmfcnf.lua?
I tried with
return { type = "configuration", version = "1.", date = "2015-03-04", time = "14:00:00", comment = "ConTeXt MkIV configuration file", author = "Ulrike Fischer", content = { variables = { TEXMFCNF = {"D:/context-minimals/context/tex/texmf/web2c"} } } }
but it didn't work ;-(. This doesn't setup the pathes.
I also tried dofile("D:/context-minimals/context/tex/texmf/web2c/texmfcnf.lua")
which didn't work either.
You can try in texmf-local/web2c: return { type = "configuration", version = "1.", date = "2015-03-04", time = "14:00:00", comment = "ConTeXt MkIV configuration file", author = "Ulrike Fischer", content = { variables = { -- texroot/texmf-mine/... TEXMFMINE = "selfautoparent:texmf-mine", TEXMF = "{$TEXMFHOME,!!$TEXMFPROJECT,!!$TEXMFFONTS,!!$TEXMFLOCAL,!!$TEXMFMODULES,!!$TEXMFCONTEXT,!!$TEXMFSYSTEM,!!$TEXMFMAIN,!!$TEXMFMINE}", } } } ----------------------------------------------------------------- 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 -----------------------------------------------------------------
Am Wed, 04 Mar 2015 17:58:24 +0100 schrieb Hans Hagen:
You can try in texmf-local/web2c: ...
This doesn't help: context never looks in texmf-local/web2c. It looks into D:/texmfcnf and then stops. But I just realized that I have actually two context (one in texlive 2014) and trying to setup the systems with a texmfcnf.lua will probably give a complete mess. So I will revert to my normal system where I change the environment variables first. -- Ulrike Fischer http://www.troubleshooting-tex.de/
On 3/4/2015 7:06 PM, Ulrike Fischer wrote:
Am Wed, 04 Mar 2015 17:58:24 +0100 schrieb Hans Hagen:
You can try in texmf-local/web2c: ...
This doesn't help: context never looks in texmf-local/web2c. It looks into D:/texmfcnf and then stops.
hm, normally it will look relative to the binary, in trees/web2c paths
But I just realized that I have actually two context (one in texlive 2014) and trying to setup the systems with a texmfcnf.lua will probably give a complete mess. So I will revert to my normal system where I change the environment variables first.
ok; taking bins from one tex tree (full tree) and expecting them to work with another one is tricky due all this auto-magic; in that case setting the TEXMF variable as environment variable might help (in general it's best to use a context garden tree with garden binaries as there we use beta bins) ----------------------------------------------------------------- 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 -----------------------------------------------------------------
Am Thu, 05 Mar 2015 01:40:06 +0100 schrieb Hans Hagen:
You can try in texmf-local/web2c: ...
This doesn't help: context never looks in texmf-local/web2c. It looks into D:/texmfcnf and then stops.
hm, normally it will look relative to the binary, in trees/web2c paths
Yes, but as I have set the environment variable TEXMFCNF I have overwritten the normal behaviour.
But I just realized that I have actually two context (one in texlive 2014) and trying to setup the systems with a texmfcnf.lua will probably give a complete mess. So I will revert to my normal system where I change the environment variables first.
ok; taking bins from one tex tree (full tree) and expecting them to work with another one is tricky due all this auto-magic; in that case setting the TEXMF variable as environment variable might help
Sorry this is a misunderstanding: I'm not trying to mix two context versions. I want to use the standalone binaries with the standalone trees, and perhaps the texlive context binaries with the texlive tree. Beside this I also want to use miktex, texlive 2014, and sometimes (for debugging) texlive 2013 ;-); Sorting out all this installations so that they don't interfer isn't easy. -- Ulrike Fischer http://www.troubleshooting-tex.de/
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. Best regards, Lukas
texmfcnf.lua (can be in your texmf-local tree) or the TEXMF env var; not so different from regular texlive, only in a different configuration file
-- Ing. Lukáš Procházka | mailto:LPr@pontex.cz Pontex s. r. o. | mailto:pontex@pontex.cz | http://www.pontex.cz Bezová 1658 147 14 Praha 4 Tel: +420 241 096 751 Fax: +420 244 461 038
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 -----------------------------------------------------------------
On 3/6/2015 10:52 AM, Hans Hagen wrote:
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
btw, this is explained in the recent workflow manual ----------------------------------------------------------------- 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 -----------------------------------------------------------------
Thanks for explanation, I didn't know about that...
Lukas
On Fri, 06 Mar 2015 10:52:47 +0100, Hans Hagen
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 ----------------------------------------------------------------- ___________________________________________________________________________________ If your question is of interest to others as well, please add an entry to the Wiki!
maillist : ntg-context@ntg.nl / http://www.ntg.nl/mailman/listinfo/ntg-context webpage : http://www.pragma-ade.nl / http://tex.aanhet.net archive : http://foundry.supelec.fr/projects/contextrev/ wiki : http://contextgarden.net ___________________________________________________________________________________
-- Ing. Lukáš Procházka | mailto:LPr@pontex.cz Pontex s. r. o. | mailto:pontex@pontex.cz | http://www.pontex.cz Bezová 1658 147 14 Praha 4 Tel: +420 241 096 751 Fax: +420 244 461 038
On 3/6/2015 1:08 PM, Procházka Lukáš Ing. - Pontex s. r. o. wrote:
Thanks for explanation, I didn't know about that...
i guess that there is a lot of stuff deep down only a few people know about (this is typical needed for more complex workflows) ... when i run into them i'll try to document them in 'workflows' but suggestions are welcome (right now Alan is updating the new publications manual which will have some 8000 pages of tricky details and hidden features that we forget about as soon as we've added them)
Lukas
On Fri, 06 Mar 2015 10:52:47 +0100, Hans Hagen
wrote: 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 ----------------------------------------------------------------- ___________________________________________________________________________________
If your question is of interest to others as well, please add an entry to the Wiki!
maillist : ntg-context@ntg.nl / http://www.ntg.nl/mailman/listinfo/ntg-context webpage : http://www.pragma-ade.nl / http://tex.aanhet.net archive : http://foundry.supelec.fr/projects/contextrev/ wiki : http://contextgarden.net ___________________________________________________________________________________
-- ----------------------------------------------------------------- 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 -----------------------------------------------------------------
Hello,
On Fri, 06 Mar 2015 14:45:44 +0100, Hans Hagen
On 3/6/2015 1:08 PM, Procházka Lukáš Ing. - Pontex s. r. o. wrote:
Thanks for explanation, I didn't know about that...
i guess that there is a lot of stuff deep down only a few people know about (this is typical needed for more complex workflows) ... when i run into them i'll try to document them in 'workflows' but suggestions are welcome
one "all-embracing" though "non-final" manual (even pasted together from various fragments) would be welcome; and is asked here in the forum from time to time (especially by newbies who suppose such document must exist).
(right now Alan is updating the new publications manual which will have some 8000 pages of tricky details and hidden features that we forget about as soon as we've added them)
Comparing with the last (AutoCAD) manual I bought: such Ctx manual in printed version would give 8 volumes with 1000 pages; each volume 50 mm thick, on a thinner paper, onto 180 x 240 mm page size. Lukas -- Ing. Lukáš Procházka | mailto:LPr@pontex.cz Pontex s. r. o. | mailto:pontex@pontex.cz | http://www.pontex.cz Bezová 1658 147 14 Praha 4 Tel: +420 241 096 751 Fax: +420 244 461 038
participants (5)
-
Gerben Wierda
-
Hans Hagen
-
Procházka Lukáš Ing. - Pontex s. r. o.
-
Ulrike Fischer
-
Wolfgang Schuster