On 08/01/2010 21:49, Frank Küster wrote: > (and similar for TEXMFSYSCONFIG). But that implies that user-changed > files there (even files that would be created by texconfig, but have not > yet been) will be respected. And I know from discussions with Thomas > that the tree was always intended as *the* place for personal or > side-wide configuration changes, respectively. That's why the tree > comes before anything else. > So, maybe I should change the search path to add TEXMF(SYS)CONFIG indeed.
> Manuel, wouldn't it be easier to simply search texdoc.cnf (and > texdoc-bin.cnf or whatever) with kpse.find_file? I haven't looked into > the code recently, but generally I think if a file looks into texmf > trees, it should use kpathsea in any case, wherever possible. > I want to read all teh configuration files, and the kpse Lua library doesn't provide a way to find all results like kpsewhich's --all option. (I wanted to request it and even began preparing a patch at some point, then it went out of my mind.) Manuel. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org