Comment 9 for bug 186164

On Tue, Mar 18, 2008 at 06:36:53AM -0000, Norbert Preining wrote:
> Huu? Example please? They do *different* things. kpsewhich gives the
> file as found by the kpse lib, while kpsewhere to (from the man page):
> kpsewhere - Expanding kpsewhich to separately iterate over each texmf
> tree listed in $TEXMF.
>
> So it is not surprising that they find different files, kpsewhere will
> find more files. Files can be shadowed by putting a file of the same
> name into a higher order directory, that is a feature.

I said `as first hit'. The example was in the original message that
you quoted.

When a tree in $TEXMF is marked by !!, but the tree does not appear
in $TEXMFDBS, then kpsewhere searches the tree whereas kpsewhich does
not. Thus kpsewhich finds nothing, and kpsewhere finds the single
matching file.

:-- George