Mailing-List: contact cygwin-help AT sourceware DOT cygnus DOT com; run by ezmlm List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner AT sources DOT redhat DOT com Delivered-To: mailing list cygwin AT sources DOT redhat DOT com Date: Mon, 10 Sep 2001 19:45:15 +0200 From: Corinna Vinschen To: "'cygwin AT cygwin DOT com'" Subject: Re: new tcsh 6.10.3 bug (regression) Message-ID: <20010910194515.A19532@cygbert.vinschen.de> Mail-Followup-To: "'cygwin AT cygwin DOT com'" References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: ; from Chris.Georges@disney.com on Sat, Sep 08, 2001 at 11:58:28PM -0400 On Sat, Sep 08, 2001 at 11:58:28PM -0400, Georges, Chris wrote: > > 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. I wouldn't name that as a bug. However, I'm looking into that issue. Corinna -- Corinna Vinschen Please, send mails regarding Cygwin to Cygwin Developer mailto:cygwin AT cygwin DOT com Red Hat, Inc. -- 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/