Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner@cygwin.com Mail-Followup-To: cygwin@cygwin.com Delivered-To: mailing list cygwin@cygwin.com From: ericblake@comcast.net (Eric Blake) To: Shankar Unni , cygwin@cygwin.com Subject: Re: tcsh can't find executables in Path with "wrong" case Date: Wed, 14 Sep 2005 02:39:26 +0000 Message-Id: <091420050239.16069.43278D5E0005121300003EC522007613940A050E040D0C079D0A@comcast.net> > It's clearly something to do with the path hashing, as unhashing fixes > this problem (typing "unhash" at the command prompt). And "bash" > doesn't seem to have this problem (I guess it doesn't hash things). Just to avoid the spread of misinformation, bash also does hashing, but it doesn't try to do case insensitive hashing. tcsh really is doing something different under the hood than bash. -- Eric Blake volunteer cygwin bash maintainer -- 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/