Re: texconfig init

> Are you saying that I shouldn't have the 
> '/usr/local/teTeX/bin/powerpc-apple-darwin-current' directory in my 
> PATH?

No, Reinhard is talking about "." being an element of your $PATH. This
is a problem if you cannot trust all users or all of the software on
your system. Someone could place a trojan horse into /tmp and you might
execute it if you "cd" into it. Even if "." is listed as last element,
you can still be hit by a typo (such as "mroe" instead of "more").

Back to your original problem: "\input texinfo" has read texinfo and
not texinfo.tex. The reason was that for the first element of TEXINPUTS
(which is "."), the system has tried to load texinfo.tex (which did not
exist in ".") and then texinfo (which succeeded). The system has then
stopped searching for texinfo.tex in other elements of your TEXINPUTS
search path (which would have been successful).

So, while the current rules for file searching can handle the situation
that a program foo and it's documentation foo.tex both exist in
"." (because foo.tex is always searched first), they have failed in this
case. On the other hand, any strategy which implements our "compiled
oral history" will have cases where it is not doing what the user wants...

Thomas