From: peter@objy.com (Peter Moore)
To: mason@werple.mira.net.au
Cc: zsh-users@math.gatech.edu
Subject: Re: zsh script can't find zsh binary?
Date: Tue, 27 Jun 95 17:39:29 PDT [thread overview]
Message-ID: <9506280039.AA13898@hoonk.objy.com> (raw)
In-Reply-To: <199506272350.JAA07735@werple03.mira.net.au> (message from Geoff Wing on Wed, 28 Jun 1995 09:50:44 +1000 (EST))
> :Jose Unpingco writes:
> :> I have a very simple script. It looks like this..
> :> #!/home/sunshine/grad/unpingco/bin/zsh
> :> echo 'hey'
> :>
> :> when I try to invoke it on the command line as
> :> zsh> cf.zsh
> :> I get
> :> zsh: command not found: cf.zsh
> :
> :This looks like a classic case of the interpreter exec line being too
> :long! One of the sillier features of unix lookalikes.
> :There is usually a limit on how long the #! line can be, 32 characters
> :or so. The error message always complains it can't find the script
> :file, not the interpreter. You've passed the length limit. This is a
> :kernel problem, rather than zsh. :-)
>
> This isn't the problem here. The limit is 64 characters, and the message for
> exceeding this is: "exec format error". (It has nothing to do with the kernel)
> Another possibility could be that the program's not in his path, and he should
> do ./cf.zsh
On which platform? On a Sun4 (SunOS 4.1.3) the limit is 32 characters
and the error message from zsh is without an explicit path for the
executable is:
zsh: command not found: fog
And the error you get with an explicit path is:
zsh: no such file or directory: ./fog
Peter Moore
peter@objy.com
next prev parent reply other threads:[~1995-06-28 0:48 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
1995-06-27 23:50 Geoff Wing
1995-06-28 0:39 ` Peter Moore [this message]
-- strict thread matches above, loose matches on Subject: below --
1995-06-25 17:20 Jose Unpingco
1995-06-27 10:41 ` Dave Sainty
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=9506280039.AA13898@hoonk.objy.com \
--to=peter@objy.com \
--cc=mason@werple.mira.net.au \
--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).