Am Thu, 09 Apr 2009 20:29:16 +0200 schrieb Hans Hagen:

>> The problems seems to be that luatools appends // only to one of my
>> roots (the last mentioned in $TEXMF). The output of the "path"
>> variable in the above code is:
>> 
>> I:/TeX-Roots/luatexmf/texmf
>> ....
>> J:/MIKTEX2.7
>> C:/Dokumente und
>> Einstellungen/Ulle/Anwendungsdaten/MiKTeX/2.7/scripts//
>> 
>> So the above test is false for most of my roots. 
>> 
>> The change doesn't help with mtxrun ;-(.
> 
> hm, but this // is determined by the configuration file texmf.cnf
> 
> tweaking the script for miktex and then breaking my own system is a bit 
> tricky
> 
> how does your texmf spec look? (the one with the //)? maybe i need to 
> fix the expander (quite tricky code)


I doubt that the problem has something to do with miktex. After all
I'm using no applications or settings from miktex, I'm only using
the roots as local roots. 

I realised that my description above was not completly exact: The
last root doesn't have an // appended but /scripts//. 

I found the function splitpathexpr and input.aux.expanded_path which
seems to get an input like

{Root1
Root2
Root2
Root4}
/tex//

where the last line depends on the file type, and the previous lines
have been made by expanding and splitting $TEXMF 
   $TEXMF = {$TEXMFMAIN;$TEXMFLOCAL;$TEXMFVAR} 


and converts this to 

Root1
Root2
Root2
Root4
/tex//

and I think that somewhere in the following processing the /<type>//
string gets appended only to the last root (Root4) instead to all
roots. (It is always the last root in $TEXMFVAR which gets the
string.) 


-- 
Ulrike Fischer 

___________________________________________________________________________________
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  : https://foundry.supelec.fr/projects/contextrev/
wiki     : http://contextgarden.net
___________________________________________________________________________________

Reply via email to