[tex-k] kpsewhich, TEXINPUTS, -expand-var, and -progname

Tom Kacvinsky tjk@ams.org
Sun, 1 Apr 2001 15:01:53 -0400 (EDT)

I meant to add I am using teTeX 1.0.7

tjk@thor:~> kpsewhich --version
kpathsea version 3.3.1
Copyright (C) 1997 K. Berry.
There is NO warranty.  You may redistribute this software
under the terms of the GNU General Public License.
For more information about these matters, see the files named COPYING.

Sorry for the omission.

On Sun, 1 Apr 2001, Tom Kacvinsky wrote:

> I am in the process of setting up some shell scripts wherby I customize search
> paths by setting the environment TEXINPUTS (I'm using tcsh).  The way I am
> customizing TEXINPUTS is by appending `:' to a `:' separated list of paths.  For
> example:
>     setenv TEXINPUTS /foo//:/bar//:
> What I would then like to see is how TEXINPUTS looks when latex, tex, pdftex,
> et. al. are invoked.  I am trying to do this by using kpsewhich:
>    kpsewhich -progname=tex -expand-var='$TEXINPUTS'
>    kpsewhich -progname=latex -expand-var='$TEXINPUTS'
>    etc...
> The output I get is simply this:
>    /foo//:/bar//:
> What I would expect to see (because of the trailing `:') is this:
>   /foo//:/bar//:<contents of TEXINPUTS.latex, TEXINPUTS.tex, etc...>
> Where the stuff in <...> depends on which program name is supplied with the
> -progname switch.
> Is this a bug in kpsewhich, or is kpsewhich acting as intended?