Mailing-List: contact cygwin-help@sourceware.cygnus.com; run by ezmlm List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner@sources.redhat.com Delivered-To: mailing list cygwin@sources.redhat.com Message-Id: From: "Georges, Chris" To: "'cygwin@cygwin.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) Content-Type: text/plain; charset="iso-8859-1" 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/