[tex-live] texdoc under windows
taco at elvenkind.com
Mon Jun 11 10:39:14 CEST 2007
Frank Küster wrote:
> Taco Hoekwater <taco at elvenkind.com> wrote:
>> Frank Küster wrote:
>>> b) kpse* in luatex?
>> I was going to say 'the reference manual' but I have done stuff in
>> the past weeks that is not in the manual yet. Because there are
>> only a few functions involved, here is the relevant documentation
>> (most have a 1-to-1 relationship with the kpathsea C functions):
> Thank you, I think that'll be enough for me.
>> "var" = kpse.expand_var("varname")
>> * expand a texmf variable (== kpsewhich --expand-var)
>> "path" = kpse.expand_path("path")
>> * expand a search path (== kpsewhich --expand-path)
>> "variable" = kpse.expand_braces("variable")
>> * expand a braced set (== kpsewhich --expand-braces)
>> If this is not good enough, let me know. Adding an interface to other
>> existing kpathsea functionality takes no more than a few minutes.
> Probably I would need the analog of kpsewhich --var-value, too:
Ok, that will be included in the next snapshot (sometime this week)
> - As long as "--all" does not work for kpsew.find_file (I guess that's
> not a problem of kpsewhich, but of the library) I need to iterate over
> the trees in TEXDOCS.
kpsewhich --all only works in combination with --path, and then it
calls a completely different library function that (seems to) test
the harddisk instead of the database. kpse_find_file() always returns
a single file, afaik.
The kpathsea headers are a bit scattered, I am not sure if there is
a possibility to get the full list of matches based on the database
(and optionally the disk as well). If it is not there, I could write
it myself of course, but it would be better if the library provided
More information about the tex-live