Mail Archives: cygwin/2001/12/13/12:33:42
> -----Original Message-----
> From: Conner, Quentin
> Sent: Thursday, December 13, 2001 11:26 AM
> To: 'vinschen AT redhat DOT com'
> Subject: Updated: tcsh-6.10.00-3
>
>
> Any workaround for the .EXE related path search problem in tcsh 6.10 for
> CYGWIN?
>
> Thanks,
>
> Quentin
> --
> 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.
>
>
> --
> Quentin Conner
> qconner AT coremetrics DOT com
> (512) 342-2623 x2206
>
--
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 -