finding locations of many files via kpse

[Mike Marchywka]

________________________________________
From: texhax <texhax-bounces+marchywka=hotmail.com at tug.org> on behalf of Karl Berry <karl at freefriends.org>
Sent: Wednesday, July 3, 2024 6:10 PM
To: erik at xerdi.com
Cc: texhax at tug.org
Subject: Re: finding locations of many files via kpse

    The first would lead to a significant change in the CLI implementation,

I don't get it. What I'm picturing is maybe a half-dozen lines of code.

    As every path then needs its own option set being preceded/post-ceded,

Didn't even occur to me. I see no need to go that way.

    or all options simply apply to every path given.

Yes.

    Both options are tricky to conclude I guess.

No, why? All options are already parsed before anything is looked up,
because that's how getopt_long_only works. --best, karl.

-------------------------------------
I guess in the little I've used this thing, the problem is the path
syntax. If the kpse utils could export a path in the normal linux
PATH syntax presumably  you could find or make some other
utility that would work with all linux PATH like variables.
IIRC there was a syntax for "include all subdirs" which would not
be hard to expand to all current subdirs.  
If nothing else, you could write a scrupt  to set PATH to the 
expanded kpse path and run which, although better have which
use some other variable for the PATH,

 which -a ls cat grep
/bin/ls
/bin/cat
/bin/grep