Corinna Vinschen wrote:
Cygwin tcsh does not share its hashing code with the Win32 version, it
uses the same code as all other OSes are using. No other OS is using
case insensitive hashing, so doesn't Cygwin tcsh.
Thanks for the corrections.
But bash is clearly doing something right, as:
bash-3.00$ ls -l /cygdrive/c/oracle/product/10.1.0/db_1/bin | grep -i
exp.exe
----------+ 1 shankar None 405776 Mar 8 2004 EXP.EXE
bash-3.00$ which exp
/cygdrive/c/oracle/product/10.1.0/db_1/bin/exp
bash-3.00$ which exp.exe
/cygdrive/c/oracle/product/10.1.0/db_1/bin/exp.exe
bash-3.00$ which EXP
/cygdrive/c/oracle/product/10.1.0/db_1/bin/EXP
bash-3.00$ which EXP.EXE
/cygdrive/c/oracle/product/10.1.0/db_1/bin/EXP.EXE
And it's able to run the program using any of those 4 unqualified names
(exp, exp.exe, EXP, EXP.EXE).
But tcsh is lost:
> which exp
exp: Command not found.
> which exp.exe
exp.exe: Command not found.
> which EXP
EXP: Command not found.
> which EXP.EXE
EXP.EXE: Command not found.
Huh? But:
> exp
exp: Command not found.
> exp.exe
exp.exe: Command not found.
> EXP
... output from Oracle EXP
> EXP.EXE
... output from Oracle EXP
I wonder if tcsh can pick up some lessons from bash...
Oh, I'm running cygwin1-20050914.dll (on top of cygwin 1.5.18-1), and
tcsh 6.14.00-5.
--
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
Problem reports: http://cygwin.com/problems.html
Documentation: http://cygwin.com/docs.html
FAQ: http://cygwin.com/faq/
