zsh-users
 help / color / mirror / code / Atom feed
From: Chavdar Ivanov <ci@delcam.com>
To: "Trinh, Timothy" <timothy.trinh@attws.com>
Cc: "'zsh-users@math.gatech.edu'" <zsh-users@math.gatech.edu>
Subject: RE: Problem running zsh on WinNT 4.0
Date: Mon, 15 Feb 1999 08:37:07 -0500 (EST)	[thread overview]
Message-ID: <Pine.HPX.4.10.9902150826180.9328-100000@marge> (raw)
In-Reply-To: <3AABFE76426DD211AC3000805FFE11768A7131@hq-msg04.nwest.mccaw.com>

On Friday Trinh, Timothy gave us enlightenment about RE: Problem running...:

> Hello ALL,
> 
> I really appreciated all the suggestion I have received regarding setting up
> the zsh program set up on WinNT40.
> I am able to start up the zsh program and have it automatically source my
> startup files.  Even though my zsh program 
> is starting up properly on my WinNT4.0, I am not able to run shell script
> like I do on Unix.  When I do an ls -l on the shell script, 
> do not see any x permissions on the shell script.  When I chmod a+x <shell
> script name>, I still do not see the x permissions on the 
> shell script.  Is there a particular way of executing the shell script via
> the zsh program on WinNT4.0?  Do I need to name the shell script in a
> certain way in order for it to execute?  I have tried including the
> following line at the beginning of the shell script:
> 
> #!c:/bin/zsh/zhs.exe 
> 
> Executing the shell script with the above line in it, I get the following
> error: zsh: exec format error: <shell script name>.
> 
> Any suggestions and comments are greatly appreciated.
> 
> Thanks,
> Timothy
> 
> PS:  Larry S.: Are there any other arguments I should be aware of in running
> the zsh program?
> 
> 	----------
> 

Use Explorer to associate files with extension, i.e., .zsh, with the zsh.
I have two actions associated with it - Edit and Run; Edit invokes pfe32
on the script, Run just runs it ( you point to your current zsh.exe
location for this to work ). 

>From CMD you can run zsh scripts by specifying the extension:

C:\ >  script.zsh

The trouble now is you apparently can not pass any parameters to the
script, therefore you might resolve to using 'read' for them in the script
itself.  Any ideas here?


----------------------------------------------------------------
Chavdar Ivanov           | Talbot Way, Small Heath Business Park
Delcam UK Limited        | Birmingham B10 0HJ, United Kingdom
Customer Support Dept.   | (+44)121-6831014
----------------------------------------------------------------
Keep Canada beautiful. Swallow your beer cans.      
----------------------------------------------------------------
Monday, February 15, 1999



  parent reply	other threads:[~1999-02-15 15:24 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
1999-02-13  0:49 Trinh, Timothy
1999-02-13  7:24 ` Bart Schaefer
1999-02-15 13:37 ` Chavdar Ivanov [this message]
  -- strict thread matches above, loose matches on Subject: below --
1999-02-20  0:40 Trinh, Timothy
1999-02-16  0:40 Amol Deshpande
1999-02-12 20:54 Amol Deshpande
1999-02-12 20:53 Trinh, Timothy
1999-02-12 19:23 Trinh, Timothy
1999-02-12 19:40 ` Larry P . Schrof
1999-02-12  1:55 Trinh, Timothy
1999-02-12 15:49 ` Larry P . Schrof
1999-02-12 17:01   ` Bart Schaefer

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=Pine.HPX.4.10.9902150826180.9328-100000@marge \
    --to=ci@delcam.com \
    --cc=timothy.trinh@attws.com \
    --cc=zsh-users@math.gatech.edu \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
Code repositories for project(s) associated with this public inbox

	https://git.vuxu.org/mirror/zsh/

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).