From: "Trinh, Timothy" <timothy.trinh@attws.com>
To: "'Bart Schaefer'" <schaefer@brasslantern.com>
Cc: "'zsh-users@math.gatech.edu '" <zsh-users@math.gatech.edu>
Subject: RE: Problem running zsh on WinNT 4.0
Date: Fri, 19 Feb 1999 16:40:05 -0800 [thread overview]
Message-ID: <3AABFE76426DD211AC3000805FFE11768A713F@hq-msg04.nwest.mccaw.com> (raw)
Hello All,
Once again I appreciated all the help that I have been given. It was
definitely a typo problem when I place the
#!c:/bin/zsh/zsh.exe in my shell scripts. After correcting the typo, the
shell script ran beautifully.
Thanks again to all who have taken the time to answer my questions,
Timothy
----------
From: Bart Schaefer[SMTP:schaefer@brasslantern.com]
Sent: Friday, February 12, 1999 11:25 PM
To: Trinh, Timothy; 'zsh-users@math.gatech.edu '
Subject: Re: Problem running zsh on WinNT 4.0
On Feb 12, 4:49pm, Trinh, Timothy wrote:
} Subject: RE: Problem running zsh on WinNT 4.0
}
} Hello ALL,
}
} 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.
There's not really any such thing as "x permission" in NT. Anything
with
the right file extension (.exe, .bat, ...) has "execute permission."
I
don't recall exactly how zsh's internal tests for executable-ness
are
resolved in Amol's port.
} Is there a particular way of executing the shell script via the
zsh
} program on WinNT4.0?
I don't believe so.
} Do I need to name the shell script in a
} certain way in order for it to execute?
Zsh first attempts to let the system run the named file, and then
when
(if) that fails it looks at it for a #! line. So ...
If you give the script a .exe extension, NT will try to run it as a
binary, I think. Not good.
If you give it a .bat extension, it'll try to run it as a batch
file.
That's probably even worse, as bits of the script might actually
look
sensible enough to the batch processor to cause something to happen.
} I have tried including the
} following line at the beginning of the shell script:
}
} #!c:/bin/zsh/zhs.exe
^^
Did you spell "zsh.exe" correctly in the shell script?
Otherwise I'm without clue.
--
Bart Schaefer Brass Lantern
Enterprises
http://www.well.com/user/barts
http://www.brasslantern.com
next reply other threads:[~1999-02-20 14:05 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
1999-02-20 0:40 Trinh, Timothy [this message]
-- strict thread matches above, loose matches on Subject: below --
1999-02-16 0:40 Amol Deshpande
1999-02-13 0:49 Trinh, Timothy
1999-02-13 7:24 ` Bart Schaefer
1999-02-15 13:37 ` Chavdar Ivanov
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=3AABFE76426DD211AC3000805FFE11768A713F@hq-msg04.nwest.mccaw.com \
--to=timothy.trinh@attws.com \
--cc=schaefer@brasslantern.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).