This is the mail archive of the
cygwin@cygwin.com
mailing list for the Cygwin project.
RE: scripts and exe file extensions in tcsh
- To: "'Patt, Vladimir'" <vladimir at emc dot co dot il>, 'cygwin Mailing List' <cygwin at cygwin dot com>
- Subject: RE: scripts and exe file extensions in tcsh
- From: "Robinow, David" <drobinow at dayton dot adroit dot com>
- Date: Mon, 30 Jul 2001 16:44:35 -0400
You may find the following reference useful
http://www.perl.com/pub/a/language/versus/csh.html
I'm no shell expert, but as far as I know there's nothing in Cygwin
preventing use of the c-shell. It's just that nobody has ported it.
I once had your problem and solved it with
cp /bin/tcsh.exe /bin/csh.exe
This is, obviously, not guaranteed to work in all cases.
As for ".exe.exe" not running, I'm curious as to how you managed to find
that out. In any case my answer is "don't do that".
-----Original Message-----
From: Patt, Vladimir [mailto:vladimir@emc.co.il]
Subject: RE: scripts and exe file extensions in tcsh
Thanks, for quick response!
My files starts with "#!/usr/bin/csh", you say that, I have to change all
scripts in c-shell's to shell, doesn't cygwin support c-shell?
Obviously "test.exe" was an example filename. The file with extension
".exe.exe" doesn't run. The file with '.exe' extension run's from path but
only if it called without extension. In UNIX I can run any file marked 'x'
executable in his attributes.
Cheers,
Vladimir
--
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/