This is the mail archive of the
cygwin
mailing list for the Cygwin project.
Re: tcsh doesn't find commands that end with .exe
On Jun 13 12:09, Volker Quetschke wrote:
> Corinna Vinschen wrote:
> >>I have the following problem with tcsh:
> >>
> >>tcsh doesn't find the program if the .exe extension is given. whoami is
> >>only an example, this also happens to other programs.
> >>
> >>[quetschke@Macros ~]$ which whoami
> >>/usr/bin/whoami
> >>[quetschke@Macros ~]$ which whoami.exe
> >>whoami.exe: Command not found.
> >>[quetschke@Macros ~]$ whoami
> >>quetschke
> >>[quetschke@Macros ~]$ whoami.exe
> >>whoami.exe: Command not found.
> >>[quetschke@Macros ~]$ /bin/which whoami.exe
> >>/usr/bin/whoami.exe
> >
> >That's by design.
> You mean the grand design that leads earth and all its inhabitants
> to eternal bliss?
>
> And if so, it seems to have a flaw:
>
> [quetschke@Macros ~]$ which cmd.exe
> /cygdrive/c/WINDOWS/system32/cmd.exe
> [quetschke@Macros ~]$ which cmd
> /cygdrive/c/WINDOWS/system32/cmd
>
> Care to elaborate where the difference comes from?
>
> Why should I not be allowed to start a program with it's
> real name? And why does it work sometimes?
Dunno why it prints cmd.exe but by design (minus flaws) tcsh only
starts applications given w/o path if the application is in the
internal hash table. The internal hash table stores the application
names w/o .exe suffix.
If you need something different: http://cygwin.com/acronyms/#PTC.
Corinna
--
Corinna Vinschen Please, send mails regarding Cygwin to
Cygwin Project Co-Leader mailto:cygwin@cygwin.com
Red Hat, Inc.
--
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/