Re: finding locations of many files via kpse

Hi Norbert,

>From my limited testing the fastest option is the last one in your list -
linking to libkpathsea from a custom executable in a low-level programming
language of choice.

That was the reason for the (still experimental) rust-kpathsea wrapper
getting created:
https://github.com/dginev/rust-kpathsea

Speed is not always the deciding factor of course.

Btw, there is a gotcha for your first approach that people should be aware
of: while found names get paths returned, missing names are simply elided.
Which means more work to figure out which returned path corresponds to
which input.

For example these calls produce identical results:

$ kpsewhich foo.sty pgf.sty bar.sty tikz.sty baz.sty
$ kpsewhich pgf.sty foo.sty bar.sty baz.sty tikz.sty
$ kpsewhich foo.sty pgf.sty tikz.sty bar.sty  baz.sty

Greetings,
Deyan


On Tue, Jul 2, 2024 at 6:16 AM Jonathan Fine <[email protected]> wrote:

> Hi Norbert
>
> Here's something that might help, depending on the numbers. On a high
> speed device, eg NVMe, populate a copy of the file system, except all files
> are empty.
>
> With kind regards
> Jonathan
>