From: "Lawrence Velázquez" <larryv@zsh.org>
To: "Steve Dondley" <s@dondley.com>
Cc: zsh-users@zsh.org
Subject: Re: Can't tell the difference in operation between PATH_SCRIPT and NO_PATH_SCRIPT
Date: Fri, 26 Jan 2024 01:25:29 -0500 [thread overview]
Message-ID: <a53de6de-52f1-4ae9-8c1d-dfbf34eb5892@app.fastmail.com> (raw)
In-Reply-To: <2CF29A22-6721-4275-8E92-7FF61CE4CDCB@dondley.com>
On Fri, Jan 26, 2024, at 12:20 AM, Steve Dondley wrote:
> OK, thanks.
>
> At the risk of dragging this on, allow me to ask this simple question
> to make sure I got it:
>
> Is there any way to run this command by itself on the command line:
>
>> setopt pathscript
>
> And have it affect the outcome of any subsequent commands? It looks
> like the answer is no.
Correct. It does not affect regular command execution (and is not
intended to).
> It looks to me like the pathscript setting can only affect future
> commands if it’s either:
>
> a) used with +o or -o as part of an argument passed directly to zsh
> while running a script
> b) or if it’s set in a .zshrc file (or other config file) and then
> sourced when a new shell (interactive mode)
Those are two ways to enable PATH_SEARCH for a new zsh process,
sure. Bart listed some more.
But "affecting future commands" is not really the way to look at
it; the option is not that general. PATH_SCRIPT affects one very
specific behavior: whether or not ''zsh foo'' searches PATH for a
script "foo" if ./foo doesn't exist. It does not affect anything
else, including PATH search *within* that script.
Probably should have asked earlier, but: What were you trying to
achieve with PATH_SEARCH, exactly?
--
vq
next prev parent reply other threads:[~2024-01-26 6:26 UTC|newest]
Thread overview: 33+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-01-26 2:00 Steve Dondley
2024-01-26 3:05 ` Lawrence Velázquez
2024-01-26 3:21 ` Steve Dondley
2024-01-26 3:30 ` Steve Dondley
2024-01-26 3:45 ` Lawrence Velázquez
2024-01-26 4:17 ` Steve Dondley
2024-01-26 4:58 ` Lawrence Velázquez
2024-01-26 5:20 ` Steve Dondley
2024-01-26 5:52 ` Bart Schaefer
2024-01-26 6:35 ` Lawrence Velázquez
2024-01-26 15:49 ` Steve Dondley
2024-01-26 16:07 ` Mark J. Reed
2024-01-26 16:41 ` Mark J. Reed
2024-01-26 17:21 ` Steve Dondley
2024-01-26 18:28 ` Ray Andrews
2024-01-26 18:38 ` Roman Perepelitsa
2024-01-26 19:17 ` Steve Dondley
2024-01-26 19:38 ` Roman Perepelitsa
2024-01-26 19:52 ` Steve Dondley
2024-01-26 20:06 ` Ray Andrews
2024-01-26 20:16 ` Lawrence Velázquez
2024-01-26 19:54 ` Ray Andrews
2024-01-26 20:05 ` Steve Dondley
2024-01-26 20:43 ` Steve Dondley
2024-01-27 2:34 ` .m0rph
2024-01-26 19:42 ` Ray Andrews
2024-01-26 20:08 ` Roman Perepelitsa
2024-01-26 20:21 ` Steve Dondley
2024-01-26 20:40 ` Ray Andrews
2024-01-26 6:25 ` Lawrence Velázquez [this message]
2024-01-26 6:42 ` Lawrence Velázquez
2024-01-26 15:27 ` Steve Dondley
2024-01-26 4:35 ` Lawrence Velázquez
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=a53de6de-52f1-4ae9-8c1d-dfbf34eb5892@app.fastmail.com \
--to=larryv@zsh.org \
--cc=s@dondley.com \
--cc=zsh-users@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).