Mailing-List:	contact cygwin-help AT sourceware DOT cygnus DOT com; run by ezmlm
List-Subscribe:	<mailto:cygwin-subscribe AT sources DOT redhat DOT com>
List-Archive:	<http://sources.redhat.com/ml/cygwin/>
List-Post:	<mailto:cygwin AT sources DOT redhat DOT com>
List-Help:	<mailto:cygwin-help AT sources DOT redhat DOT com>, <http://sources.redhat.com/ml/#faqs>
Sender:	cygwin-owner AT sources DOT redhat DOT com
Delivered-To:	mailing list cygwin AT sources DOT redhat DOT com
Message-Id:	<F539F53ECAF5D111B73D00805F65BAE601595EC7@WDIGL003>
From:	"Georges, Chris" <Chris DOT Georges AT disney DOT com>
To:	"'cygwin AT cygwin DOT com'" <cygwin AT cygwin DOT com>
Subject:	new tcsh 6.10.3 bug (regression)
Date:	Sat, 8 Sep 2001 23:58:28 -0400
MIME-Version:	1.0
X-Mailer:	Internet Mail Service (5.5.2653.19)

There is a new cygwin-specific bug that was introduced in tcsh between
versions 6.09 and the current 6.10.3. I'm hoping whoever made those changes
is on this list and can take a look at this issue.  The problem is that tcsh
no longer recognizes any *.EXE file on the path as executable, unless its
name is all lower case letters.  Typing 'cl' if CL.EXE is on the path
results in 'Command not found'.  The same thing occurs if you type 'CL' or
'CL.EXE'.  If you run tcsh 6.09 (on cygwin 1.3.2), typing 'cl' will run the
'CL.EXE' that is on the path.  At the very least, tcsh should respond to
providing the full executable name in capitals, and it would be convenient
if it was case-insensitive like the win2k cmd shells are and like what it
did in 6.09.

Thanks,
chris


--
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/

- Raw text -