Mailing-List: contact cygwin-help AT sourceware DOT cygnus DOT com; run by ezmlm
List-Subscribe: <mailto:cygwin-subscribe AT sources DOT redhat DOT com>
List-Archive: <http://sources.redhat.com/ml/cygwin/>
List-Post: <mailto:cygwin AT sources DOT redhat DOT com>
List-Help: <mailto:cygwin-help AT sources DOT redhat DOT com>, <http://sources.redhat.com/ml/#faqs>
Sender: cygwin-owner AT sources DOT redhat DOT com
Delivered-To: mailing list cygwin AT sources DOT redhat DOT com
Message-ID: <75E2893D8DAFD411BADE00D0B7696457092514@dimona.emc.co.il>
From: "Patt, Vladimir" <vladimir AT emc DOT co DOT il>
To: "'cygwin Mailing List'" <cygwin AT cygwin DOT com>
Subject: RE: scripts and exe file extensions in tcsh
Date: Mon, 30 Jul 2001 19:41:41 +0300
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2650.21)
Content-Type: text/plain;
	charset="iso-8859-1"

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

-----Original Message-----
From: David Starks-Browning [mailto:starksb AT ebi DOT ac DOT uk]
Sent: Mon, July 30, 2001 18:32
To: Patt, Vladimir
Cc: cygwin AT cygwin DOT com
Subject: scripts and exe file extensions in tcsh


On Monday 30 Jul 01, Patt, Vladimir writes:
> Hi,
> 
> I'm just installed cygwin on my nt2K. I'm new with cygwin ...

In that case, you should read the documentation.  Such as the FAQ.

> ... so I've three questions.
> 1. Running tcshell trying to run UNIX scripts but only one with no
extension
> can run otherwise I'm getting "Command not found" error message. I already
> specified "./" in path environment variable. 

Read the FAQ entry "Why doesn't my shell script work?"

> 2. Also there is a problem to run binary file called "test.exe.exe", but
if
> it called "test.exe" only "test" (without extension) command can execute a
> program. 

"test" is a bad choice for a program name, because it conflicts with
/bin/test and possibly a shell builtin.  You should rule that out
before reporting problems running "test.exe".

> 3. And third. Path specified with single slash passed to "cd" command is
not
> understood by shell when running script, only double slash understood by
> shell. Also if this path string specified as parameter to some my program
> slashes are ignored.

Are you talking about the forward or backward slash character?  The
forward slash ('/') is the directory separator in UNIX and Cygwin.
The backward slash ('\') is the directory separator in Windows, and is
an escape character in UNIX and Cygwin shells (bash, tcsh).

See also the FAQ entry "How do I convert between Windows and UNIX
paths?"

Hope this helps.

David
(Cygwin FAQ maintainer)


--
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/


--
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/