From: Peter Stephenson <p.w.stephenson@ntlworld.com>
To: zsh-workers@zsh.org
Subject: Re: loading user startup files for zsh scripts
Date: Fri, 11 Feb 2011 19:25:17 +0000 [thread overview]
Message-ID: <20110211192517.2f16b49b@pws-pc.ntlworld.com> (raw)
In-Reply-To: <m339nucz7o.fsf@klanderman.net>
On Fri, 11 Feb 2011 11:28:43 -0500
Greg Klanderman <gak@klanderman.net> wrote:
> This appears to be due to support for the (undocumented) PATHSCRIPT
> option, whereby the path is searched for the runscript, and therefore
> the startup files must be read first so that PATH can be set properly.
It's not undocumented.
pindex(PATH_SCRIPT)
pindex(NO_PATH_SCRIPT)
pindex(PATHSCRIPT)
pindex(NOPATHSCRIPT)
cindex(path search, for script argument to shell)
item(tt(PATH_SCRIPT) <K> <S>)(
If this option is not set, a script passed as the first non-option argument
to the shell must contain the name of the file to open. If this
option is set, and the script does not specify a directory path,
the script is looked for first in the current directory, then in the
command path. See
ifnzman(noderef(Invocation))\
ifzman(the section INVOCATION in zmanref(zsh)).
)
--
Peter Stephenson <p.w.stephenson@ntlworld.com>
Web page now at http://homepage.ntlworld.com/p.w.stephenson/
prev parent reply other threads:[~2011-02-11 19:25 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-02-07 20:34 Greg Klanderman
2011-02-08 5:33 ` Bart Schaefer
2011-02-08 17:09 ` Greg Klanderman
2011-02-08 17:20 ` Peter Stephenson
2011-02-09 0:37 ` Greg Klanderman
2011-02-09 4:58 ` Bart Schaefer
2011-02-09 15:32 ` Greg Klanderman
2011-02-09 16:01 ` Greg Klanderman
2011-02-09 16:53 ` Bart Schaefer
2011-02-10 16:30 ` Greg Klanderman
2011-02-10 17:52 ` Bart Schaefer
2011-02-10 23:10 ` Greg Klanderman
2011-02-11 1:42 ` Greg Klanderman
2011-02-11 3:29 ` Bart Schaefer
2011-02-11 16:28 ` Greg Klanderman
2011-02-11 17:26 ` Bart Schaefer
2011-02-11 17:47 ` Peter Stephenson
2011-02-11 18:36 ` Bart Schaefer
2011-02-11 19:25 ` Peter Stephenson [this message]
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=20110211192517.2f16b49b@pws-pc.ntlworld.com \
--to=p.w.stephenson@ntlworld.com \
--cc=zsh-workers@zsh.org \
/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).