This is the mail archive of the cygwin mailing list for the Cygwin project.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

Re: executing .bat & .cmd files with 1.7


On Dec 17 19:41, Andy Koppe wrote:
> 2010/12/17 Vincent CÃtÃ-Roy:
> > I'm sorry, I wasn't very clear: Âxyz.bat or xyz.cmd do indeed execute
> > as before. My problem is that when I type xyz (i.e. without the
> > extension) it won't find xyz.bat or xyz.cmd, as it did before
> > upgrading.
> 
> It did not do that. Not on the Cygwin 1.5.25 install here anyway.

Maybe Vincent is using tcsh.  Older tcsh took .bat and .cmd extensions
into account, newer versions don't.  That's a deliberate change since
the behaviour diverged from the standard POSIX behaviour.  If you
have a shell script called "foo.sh" or "foo.csh", you have to give
the full name "foo.sh" or "foo.csh".  You can't start them just
specifying "foo".  In Cygwin, only the .exe and .lnk suffixes have a
special meaning for obvious reasons.


Corinna

-- 
Corinna Vinschen                  Please, send mails regarding Cygwin to
Cygwin Project Co-Leader          cygwin AT cygwin DOT com
Red Hat

--
Problem reports:       http://cygwin.com/problems.html
FAQ:                   http://cygwin.com/faq/
Documentation:         http://cygwin.com/docs.html
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]