I don't think this is a BASH issue, except possibly if your previous BASH was a version that used a different algorithm for choosing which startup scripts to execute. How long has Cygwin had the "/etc/profile.d/" directory? I thought it was recent, but I see references in the mailing list going back over a year.
On my system I see "kpsexpand" being invoked in "/etc/profile.d/lilypond-profile.sh", but of course you'd have to have lilypond installed to have that profile in place.
According to <http://cygwin.com/packages/> / <http://cygwin.com/cgi-bin2/package-grep.cgi?grep=kpsexpand>, it's supplied by the "tetex" package.
Once that package is installed, kpsexpand has a man page, but not one of its own. It's documented on the "kpsetool" man page. The "apropos" or "man -k" command is convenient for discovering this sort of thing.
Randall Schulz
Mountain View, CA USA
At 19:12 2002-11-28, Peter S Tillier wrote:
Folks,
Ever since a recent upgrade to my Cygwin installation I have been getting the following lines on starting up Cygwin:
BASH: kpsexpand: command not found
Welcome to bash version 2.05b.0(7)-release
Any ideas where the kpsexpand is coming from please? I have tried searching the list downloads and the User Guide without finding it.
TIA
Peter
-- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Bug reporting: http://cygwin.com/bugs.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/
