Oliver Buerschaper wrote: > > I was referring to > > setuptex.sh
All scripts starting with setuptex have the same functionality: they set up all the needed environment variables I have seen the following, that only differ per platform: setuptex,setuptex.sh % unix bash shell setuptex.csh % unix csh shell setuptex.bat,setuptex.cmd % windows shell > setuptex.tmf This one can be used by texmfstart if you run it with texmfstart --tree= and is only for advanced use. > context.cnf this file is not used, ever. > texmf.cnf This is read by mkii (in the normal way, via kathsea, as well as via texmfstart's file searching routines) and in mkiv by luatools when --generate is given on the command line (the rest of mkiv uses preprocessed data from the cache). As of this morning, we also have > texmfcnf.lua that is always read by all of mkiv. > environment variables These are set up by setuptex, but I assume you want to know what each does. Will you still care if they go away anyway? digging this information up though all the nooks and crannies of mkii is quite a bit of work. > and how the information contained therein is accessed (if at all) by the > different engines and scripts. More or less the same question again. How much of this do you really need to know? Because generally speaking, there are more sensible things to do than to document all thoses lines of code in a separate implementation manual. If you are curious about a few variables, can you please post which ones? Best wishes, Taco _______________________________________________ dev-context mailing list dev-context@ntg.nl http://www.ntg.nl/mailman/listinfo/dev-context
